New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Resolve Conversation

by NomaDamas in NomaDamas/AutoRAG-Research

Process [APPROVE] and [IGNORE] replies on /refactor review threads.

Apache-2.0Auto-check: notesBackend & APIs

Install Resolve Conversation

skills CLI
$ npx skills add NomaDamas/AutoRAG-Research --skill resolve-conversation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NomaDamas/AutoRAG-Research resolve-conversation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NomaDamas/AutoRAG-Research.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/resolve-conversation .claude/skills/resolve-conversation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
resolve-conversation
GitHub stars
149
Token cost
~1.5k tokens
SKILL.md length
601 words
Files
1
Skills in repo
7
Repo updated
First seen
Licence
Apache-2.0

At a glance

Process [APPROVE] and [IGNORE] replies on /refactor review threads.

  • Works in 8 steps: Verify PR Exists → Get Repository Identity → Fetch All Review Threads via GraphQL → …
  • Tasks that involve Refactoring
  • SKILL.md covers Step 1: Verify PR Exists, Step 2: Get Repository Identity, Step 3: Fetch All Review… and Step 4: Identify Actionable…, plus 5 more sections
  • Calls git, make and gh

What it does

Resolve Conversation is an agent skill from NomaDamas/AutoRAG-Research. Process [APPROVE] and [IGNORE] replies on /refactor review threads. Applies approved fixes to the codebase, resolves all responded threads on GitHub, commits and pushes changes. Sequential single-agent workflow. All output is in English.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Backend & APIs, covering Refactoring. It works with GitHub and GraphQL. The repository describes itself as: Automate your RAG research. The licence is Apache-2.0.

When your agent uses it

  • Tasks that involve Refactoring

Example prompts

  • “/resolve-conversation”

Requirements

  • Pre-approved tools (allowed-tools): Bash, Read, Write, Edit, Grep, Glob

Workflow steps

8 steps, taken from the step headings in SKILL.md.

  1. Verify PR Exists
  2. Get Repository Identity
  3. Fetch All Review Threads via GraphQL
  4. Identify Actionable Threads
  5. Process APPROVE Threads
  6. Resolve All Actionable Threads
  7. Commit and Push
  8. Report to User

What it can do on your machine

Read from SKILL.md and the folder at commit a473cf0. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash
    • Read
    • Write
    • Edit
    • Grep
    • Glob

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • make
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Resolve Conversation loads about 1.5k tokens when it runs. Until then it costs about 65 tokens; SKILL.md has 601 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~65
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Bash, Read, Write, Edit, Grep, Glob

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NomaDamas/AutoRAG-Research at commit a473cf0, republished under its Apache-2.0 licence (© NomaDamas). 601 words, ~1,490 tokens.

Download SKILL.mdSave it as .claude/skills/resolve-conversation/SKILL.md (or your agent's skills folder).
name
resolve-conversation
description
Process [APPROVE] and [IGNORE] replies on /refactor review threads. Applies approved fixes to the codebase, resolves all responded threads on GitHub, commits and pushes changes. Sequential single-agent workflow. All output is in English.
allowed-tools
Bash, Read, Write, Edit, Grep, Glob

/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:

bash
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 number
  • PR_URL -- the PR URL
  • PR_TITLE -- the PR title
  • HEAD_REF -- head branch name
  • BASE_REF -- base branch name

Step 2: Get Repository Identity

Run these commands in parallel:

bash
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/repo
  • HEAD_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:

bash
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:

  1. Thread is unresolved (isResolved == false)
  2. 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

Precedence rule: If a thread has both [APPROVE] and [IGNORE] in different replies, [APPROVE] takes precedence.

Classify each actionable thread as either APPROVE or IGNORE.

If no actionable threads are found, exit immediately:

No actionable threads found. Reply with [APPROVE] or [IGNORE] on /refactor review comments first.

Step 5: Process APPROVE Threads

For each thread classified as APPROVE, in order:

5a. Extract the Suggested Fix

From the first comment (the /refactor comment), extract the text after **Suggested Fix**:. This is the code change to apply.

Also extract:

  • path -- the file path from the thread
  • line / startLine -- the line number(s) from the thread
5b. Check File Exists

If the target file no longer exists:

  • Note in report: "File {path} no longer exists, skipping fix"
  • Still mark this thread for resolution in Step 6
  • Continue to next thread
5c. Apply the Fix
  1. Read the target file using the Read tool
  2. Apply the suggested fix using the Edit tool
  3. Run make check to validate
Show full SKILL.md (240 more words)Show less
5d. Validate

If make check fails:

  • Revert the file: git checkout -- {path}
  • Note in report: "Fix for {path}:{line} failed validation, reverted"
  • Still mark this thread for resolution in Step 6

If make check passes:

  • Note in report: "Fix applied to {path}:{line}"

Step 6: Resolve All Actionable Threads

For EVERY actionable thread (both APPROVE and IGNORE), resolve it via GraphQL mutation:

bash
gh api graphql -f query='
mutation($threadId: ID!) {
  resolveReviewThread(input: {threadId: $threadId}) {
    thread {
      isResolved
    }
  }
}' -f threadId='{THREAD_ID}'

Replace {THREAD_ID} with the thread's id from the GraphQL response.

Process all threads. If a resolve mutation fails for a specific thread:

  • Log the error
  • Continue with remaining threads
  • Note in report: "Failed to resolve thread for {path}:{line}"

Step 7: Commit and Push

If any fixes were successfully applied (not reverted) in Step 5:

bash
git add <list of fixed files>
git commit -m "fix: apply approved review suggestions from /resolve-conversation"
git push

If git push fails:

  • Inform user: "Commit created locally but push failed. Run git push manually."

If no fixes were applied (all were IGNORE or all APPROVE fixes failed validation):

  • Skip this step entirely

Step 8: Report to User

Print a final summary to the console. No emojis. Include:

/resolve-conversation complete.

Threads processed: {total_actionable}
  APPROVE: {approve_count} ({fixes_applied} applied, {fixes_failed} failed validation)
  IGNORE: {ignore_count}
Threads resolved: {resolved_count} ({resolve_failed} failed to resolve)

{If fixes_applied > 0:}
Changes committed and pushed.

{If fixes_applied > 0 and push_failed:}
Changes committed locally. Run `git push` manually.

PR: {PR_URL}

If any fixes failed validation, list them:

Failed fixes:
  - {path}:{line}: {reason}

If any files no longer exist, list them:

Skipped (file missing):
  - {path}

Error Handling

ScenarioAction
No PR foundExit with message
GraphQL query failsExit with message
No actionable threadsExit with message
make check fails after fixRevert file, still resolve thread, note in report
Resolve mutation failsLog error, continue with remaining
git push failsInform user to push manually
File no longer existsSkip fix, still resolve, note in report

© NomaDamas, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/resolve-conversation of NomaDamas/AutoRAG-Research.

Open the folder on GitHubat commit a473cf0

Compare with similar skills

Resolve Conversation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Resolve Conversation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Resolve Conversation this skillNomaDamas/AutoRAG-Research149—~1.5kAutomated safety check: NotesApache-2.0
Dev Rulesrust-dd/tako162—~810Automated safety check: PassMIT
Release WorkflowGoldziher/spikard123—~909Automated safety check: PassMIT
Review PR Commentslatitude-dev/latitude-llm4.7k—~2.6kAutomated safety check: PassMIT
Copilot PR Autopilotgithub/awesome-copilot40k—~3.4kAutomated safety check: PassMIT
GitHub Opsdaymade/claude-code-skills1.4k—~3.8kAutomated safety check: PassMIT

Similar skills

  • Dev Rules

    rust-dd/tako

    General coding-style rules to apply to every project. An agent skill from rust-dd/tako.

    162 GitHub stars~810 tokensUpdated 8 days ago
    Backend & APIsAuto-check passed

  • Release Workflow

    Goldziher/spikard

    Release/publish the spikard Rust core crate and CLI end-to-end.

    123 GitHub stars~909 tokensUpdated 6 days ago
    Backend & APIsAuto-check passed

  • Review PR Comments

    latitude-dev/latitude-llm

    Triages a PR with GitHub CLI: loads issue-level and inline review feedback (gh pr view, gh api REST, gh api graphql as appropriate), walks items in order, replies in the correct thread, optional…

    4.7k GitHub stars~2.6k tokensUpdated yesterday
    Backend & APIsAuto-check passed

  • Copilot PR Autopilot

    github/awesome-copilot

    Official

    Copilot left 14 review comments on your PR — half are nits. An agent skill from github/awesome-copilot.

    40k GitHub stars~3.4k tokensUpdated today
    Backend & APIsAuto-check passed

  • GitHub Ops

    daymade/claude-code-skills

    Operates GitHub via gh CLI and REST/GraphQL — PRs, issues, Actions, repos, collaborators, org permissions, 2FA — with explicit target, authorization, and independent readback.

    1.4k GitHub stars~3.8k tokensUpdated today
    Backend & APIsAuto-check passed

  • Linear SDK Patterns

    jeremylongshore/tons-of-skills-marketplace

    Implement current Linear TypeScript SDK query, mutation, pagination, raw GraphQL, and error-handling patterns.

    2.8k GitHub stars~1.2k tokensUpdated today
    Backend & APIsAuto-check passed

More from NomaDamas/AutoRAG-Research

  • Autorag Query

    NomaDamas/AutoRAG-Research

    Query AutoRAG-Research pipeline results using natural language.

    149 GitHub stars~1.6k tokensUpdated 2 mo ago
    Auto-check: notes

  • Create Generation Plugin

    NomaDamas/AutoRAG-Research

    Guide developers through creating a custom generation pipeline plugin for AutoRAG-Research.

    149 GitHub stars~871 tokensUpdated 2 mo ago
    Auto-check: notes

  • Create Ingestor Plugin

    NomaDamas/AutoRAG-Research

    Guide developers through creating a custom data ingestor plugin for AutoRAG-Research.

    149 GitHub stars~1.2k tokensUpdated 2 mo ago
    Auto-check: notes

  • Create Metric Plugin

    NomaDamas/AutoRAG-Research

    Guide developers through creating a custom evaluation metric plugin for AutoRAG-Research.

    149 GitHub stars~859 tokensUpdated 2 mo ago
    Auto-check: notes

  • Create Retrieval Plugin

    NomaDamas/AutoRAG-Research

    Guide developers through creating a custom retrieval pipeline plugin for AutoRAG-Research.

    149 GitHub stars~728 tokensUpdated 2 mo ago
    Auto-check: notes

  • Refactor

    NomaDamas/AutoRAG-Research

    Orchestrate a 3-agent PR code review debate using Claude Code Teams.

    149 GitHub stars~4.4k tokensUpdated 2 mo ago
    Auto-check: notes

Works with

Categories

Questions about Resolve Conversation

What does Resolve Conversation do?

Process [APPROVE] and [IGNORE] replies on /refactor review threads. Resolve Conversation is an agent skill from NomaDamas/AutoRAG-Research. Process [APPROVE] and [IGNORE] replies on /refactor review threads.

When should I use Resolve Conversation?

Resolve Conversation fits situations like: tasks that involve Refactoring.

How do I install Resolve Conversation in Claude Code?

Run `npx skills add NomaDamas/AutoRAG-Research --skill resolve-conversation -a claude-code`. Or copy the skill folder (.claude/skills/resolve-conversation in NomaDamas/AutoRAG-Research) into .claude/skills/resolve-conversation in your project. Claude Code loads it when a task matches its description.

How do I install Resolve Conversation in Codex?

Run `npx skills add NomaDamas/AutoRAG-Research --skill resolve-conversation -a codex`. Or copy the skill folder (.claude/skills/resolve-conversation in NomaDamas/AutoRAG-Research) into .agents/skills/resolve-conversation in your project. Codex loads it when a task matches its description.

Can I use Resolve Conversation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NomaDamas/AutoRAG-Research --skill resolve-conversation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/resolve-conversation, .gemini/skills/resolve-conversation, .github/skills/resolve-conversation and .opencode/skills/resolve-conversation in your project.

What does Resolve Conversation need to run?

Going by SKILL.md and its folder, Resolve Conversation needs the command-line tools its instructions call (git, make and gh). Its frontmatter pre-approves these tools: Bash, Read, Write, Edit, Grep, Glob.

Does Resolve Conversation access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Resolve Conversation safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Resolve Conversation use?

Resolve Conversation is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Resolve Conversation use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Resolve Conversation?

Skills that share tags, products or a category with Resolve Conversation: Dev Rules (rust-dd/tako, 162 stars), Release Workflow (Goldziher/spikard, 123 stars), Review PR Comments (latitude-dev/latitude-llm, 4.7k stars) and Copilot PR Autopilot (github/awesome-copilot, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Resolve Conversation?

NomaDamas (a GitHub organization) maintains it in NomaDamas/AutoRAG-Research, which has 149 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on August 9, 2026.

Source: NomaDamas/AutoRAG-Research on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.