mcpField
R
resolve-pr-comments

resolve-pr-comments

github.com/fcakyonTesting & quality1.2k38 installsUpdated today
Repository

About resolve-pr-comments

A skill for reviewing unresolved pull request comments, applying valid code fixes across matching locations, and preparing replies for comments that need no change. It uses an available subagent when possible or follows a documented GitHub CLI workflow.

Key features

  1. 01Find unresolved PR review threads
  2. 02Fix valid concerns across the codebase
  3. 03Draft replies for non-code comments
  4. 04Use subagent or manual GitHub CLI steps

Use cases

  1. 01Resolve review feedback on a pull request
  2. 02Find repeated instances of a reported code issue
  3. 03Prepare replies before posting to reviewers

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/fcakyon/claude-codex-settings --skill resolve-pr-comments

After installing, type/resolve-pr-commentsin Claude Code to confirm it loaded.

Details

From the project README

Resolve PR Comments

Analyze unresolved PR review comments, fix valid concerns, and draft responses for comments that do not require code changes.

When explicitly invoked with extra text, treat that text as the PR number or URL. If no PR reference is provided, infer it from the current branch.

Process

  1. Preferred execution

    • If subagents are available, use github-dev:pr-comment-resolver and pass the PR reference.
    • Otherwise follow the manual steps below.

  2. Fetch unresolved comments

    • If a PR number or URL is provided, use it directly.
    • Otherwise auto-detect the PR from the current branch with gh pr view --json number,headRefName.
    • Fetch inline comments with gh api repos/{owner}/{repo}/pulls/{number}/comments.
    • Fetch review-level comments with gh pr view <number> --json reviews,comments.
    • Filter to unresolved or pending threads.

  3. Resolve each comment

    • If the comment is valid, fix the code and search the codebase for the same problem in other locations.
    • Fix all matching occurrences, not just the location mentioned in the comment.
    • If the comment does not require a code change, draft a concise reply.
    • If the comment is from a bot, reply with a direct factual sentence and no pleasantries.

  4. Reply style

    • Start in lowercase.
    • Use simple language and short sentences.
    • Avoid end punctuation when possible.
    • Be concise and polite when replying to real people.

  5. Never auto-submit

    • Present all draft responses before posting them.
    • Reply comments are posted directly with gh api repos/{owner}/{repo}/pulls/{number}/comments/{comment_id}/replies -f body="..." (the {number} PR number is required, the endpoint 404s without it).
    • Add a random 3-5 second delay between posted replies with sleep $((RANDOM % 3 + 3)).

Comments

Markdown supported