Borrowing it
Nothing to install: this file belongs to NomaDamas/AutoRAG-Research. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/NomaDamas/AutoRAG-Research/main/.claude/skills/resolve-conversation/SKILL.mdgit clone --depth 1 https://github.com/NomaDamas/AutoRAG-ResearchWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/nomadamas/autorag-research/resolve-conversation)<a href="https://agentmods.dev/skills/nomadamas/autorag-research/resolve-conversation"><img src="https://agentmods.dev/badge/skills/nomadamas/autorag-research/resolve-conversation/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/nomadamas/autorag-research/resolve-conversation"><img src="https://agentmods.dev/badge/skills/nomadamas/autorag-research/resolve-conversation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00056 | $0.01510 |
| Opus 5 | $0.00028 | $0.00755 |
| Sonnet 5 | $0.00011 | $0.00302 |
| Haiku 4.5 | $0.00006 | $0.00151 |
Grade A, and why
resolve-conversation scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/resolve-conversation -- Process /refactor Review Thread Replies
You process human replies on /refactor inline PR comments. Follow these 8 steps exactly.
Step 1: Verify PR Exists
Run:
gh pr view --json number,url,title,headRefName,baseRefName
If the command fails, exit immediately:
No PR found on the current branch. Create a PR first.
Extract and remember these values:
PR_NUMBER-- the PR numberPR_URL-- the PR URLPR_TITLE-- the PR titleHEAD_REF-- head branch nameBASE_REF-- base branch name
Step 2: Get Repository Identity
Run these commands in parallel:
git remote get-url origin
git rev-parse HEAD
Parse the remote URL to extract OWNER/REPO (handle both HTTPS and SSH formats).
Store:
OWNER_REPO-- e.g.owner/repoHEAD_SHA-- current HEAD commit SHA
Step 3: Fetch All Review Threads via GraphQL
Run a single GraphQL query to fetch all review threads with their comments:
gh api graphql -f query='
query($owner: String!, $repo: String!, $pr: Int!) {
repository(owner: $owner, name: $repo) {
pullRequest(number: $pr) {
reviewThreads(first: 100) {
nodes {
id
isResolved
comments(first: 50) {
nodes {
body
author {
login
}
}
}
path
line
startLine
}
}
}
}
}' -F owner='{OWNER}' -F repo='{REPO}' -F pr={PR_NUMBER}
Replace {OWNER}, {REPO}, and {PR_NUMBER} with the values from Steps 1-2.
If the query fails, exit immediately:
GraphQL query failed. Check your GitHub authentication and permissions.
Step 4: Identify Actionable Threads
From the GraphQL response, filter threads that meet ALL of these criteria:
- Thread is unresolved (
isResolved == false) - A reply exists with a human action -- any comment after the first contains:
[APPROVE]-- human approves the suggested fix[IGNORE]-- human wants to ignore this finding
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 223 lines · 56 tokens per session scan A 489bb5ad1f27
resolve-conversation is a skill published in the GitHub repository NomaDamas/AutoRAG-Research (148 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,510 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
work-unit-commits
Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.
github-contributor
End-to-end playbook for shipping high-quality pull requests to open-source projects you don't maintain — discovery, CONTRIBUTING compliance, PR-size check, minimal-diff implementation, PR description with AI-assisted disclosure, conflict resolution, and post-submission maintainer interaction. Use whenever creating…