pr-fix-comments

PR Fix Comments

Iteratively resolve all code review comments on a GitHub pull request until the automated reviewer (or human reviewer) has no remaining feedback.

Inputs

The user provides one of:

• A GitHub PR URL (e.g. https://github.com/owner/repo/pulls/13)
• A PR number with the repo context already established
• "this PR" when the current branch already has an open PR

Extract the owner, repo, and PR number from whichever form is given.

Workflow

Repeat the following cycle until no new review comments appear:

1. Gather context

Fetch in parallel:

• PR metadata: gh pr view <N> --json title,body,headRefName,baseRefName,state
• All review comments (top-level only — in_reply_to_id == null):

  gh api repos/{owner}/{repo}/pulls/{N}/comments \
    --jq '.[] | select(.in_reply_to_id == null) | {id, path, line, body, created_at, user: .user.login, diff_hunk}'
  

2. Identify unaddressed comments

A comment is unaddressed if no reply exists from a non-bot user. Check by collecting all in_reply_to_id values and filtering out top-level comments whose id appears as a reply target.

Shortcut: if a comment already has a reply from ebragas (or the repo owner), treat it as addressed.

If no unaddressed comments remain, the cycle is done — report success and stop.

3. Checkout the PR branch

If you're already on the correct branch (e.g., inside a worktree from /execute-task), skip the checkout.

Otherwise:

git fetch origin <headRefName>
git checkout <headRefName>

If a worktree conflict blocks checkout, remove the stale worktree first.

4. Triage each comment

For each unaddressed comment, read the referenced file and surrounding context. Decide:

• Fix — the comment identifies a real issue (wrong token, missing prop, broken test, inconsistent pattern, actual bug). Apply the fix.
• Skip — the comment is stylistic preference with no functional impact, is factually wrong, or conflicts with project conventions. Note the reason.

Bias toward fixing. Only skip when the suggestion would make things worse or is clearly incorrect.

5. Apply fixes

Edit the files directly. Prefer Edit tool over Write for surgical changes.

6. Verify

Run the project's test, build, and lint commands. For this project:

npx vitest run <relevant-test-files>
npm run build
npx eslint <changed-files>   # lint only changed files to avoid noise from dist/worktrees

If verification fails, fix the issue before proceeding.

7. Commit and push

Stage only the changed files (not unrelated files). Commit with a descriptive message summarizing the fixes. Push to the PR branch.

git add <specific-files>
git commit -m "<message>"
git push origin <branch>

8. Reply to each comment

For each comment that was fixed or skipped, post a reply via the API:

gh api repos/{owner}/{repo}/pulls/{N}/comments/{comment_id}/replies \
  -f body="<one-sentence response>"

Reply format:

• Fixed: "Fixed — ."
• Skipped: "Skipped — ."

9. Re-request review

gh pr edit <N> --add-reviewer 'copilot-pull-request-reviewer'

For human reviewers, use their GitHub username instead.

10. Wait for review

Poll until the review count increases or the pending reviewer clears:

# Check review count
gh api repos/{owner}/{repo}/pulls/{N}/reviews \
  --jq '[.[] | select(.user.login == "<reviewer>")] | length'

# Check if still pending
gh api repos/{owner}/{repo}/pulls/{N}/requested_reviewers \
  --jq '.users[].login'

Wait 30-60 seconds between polls. Once the new review lands, go back to step 1.

11. Completion

When a review cycle produces zero new unaddressed comments, report:

• Total rounds completed
• Total comments fixed vs skipped
• Final review status

Tips

• Fetch PR details and comments in parallel to save time.
• Launch all comment replies in parallel since they're independent.
• When editing multiple files for the same review round, make all edits, then run verification once, then commit once — don't commit per-comment.
• If the reviewer keeps flagging the same pattern across files (e.g., wrong token class), grep the entire PR diff for other instances and fix them all proactively to avoid another round.