Triage and resolve GitHub PR review comments one by one, interactively. Use when the user asks to handle, address, respond to, or resolve PR review comments, or mentions reviewer feedback on a pull request.
76
94%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Evaluate review comments on the PR (from the current branch, or a PR number/URL if given). For each unresolved comment: summarize the feedback, suggest a resolution, ask the user how to resolve it, apply their choice, commit if needed, and resolve the thread.
Find the PR. Use the given number/URL, else derive it from the current branch (gh pr view). Stop if no PR exists.
Fetch unresolved review threads via the GraphQL reviewThreads field on the pull request — request each thread's id, isResolved, isOutdated, path, line, and comments. Filter to isResolved == false. (Use GraphQL, not REST: only it exposes thread ids and resolution state.)
Loop one comment at a time. For each: (a) summarize the feedback + file/line, reading surrounding code; (b) suggest a concrete fix; (c) ask via AskQuestion with options — apply suggested fix / apply a different fix / reply only / skip; (d) apply the choice; (e) if applicable, summarize what was changed and ask whether to commit; (f) resolve the thread via the GraphQL resolveReviewThread mutation.
Report an overview of what was changed, committed, replied to, skipped, and resolved. Include links.
8403f24
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.