From agent-reviews
Automatically resolves all PR review comments (human and bot) by fetching unanswered comments, evaluating each, fixing real issues, dismissing false positives, and replying with outcomes.
How this skill is triggered — by the user, by Claude, or both
Slash command
/agent-reviews:resolve-reviewsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Automatically resolve all review comments (both human and bot) on the current PR. Uses a two-phase workflow: fix all existing issues, then poll for new ones until quiet.
Automatically resolve all review comments (both human and bot) on the current PR. Uses a two-phase workflow: fix all existing issues, then poll for new ones until quiet.
All commands below use npx agent-reviews. If the project uses a different package manager, substitute the appropriate runner (e.g., pnpm dlx agent-reviews for pnpm, yarn dlx agent-reviews for Yarn, bunx agent-reviews for Bun). Honor the user's package manager preference throughout.
Cloud environments only (e.g., Codespaces, remote agents): verify git author identity so CI checks can map commits to the user. Run git config --global --get user.email and if empty or a placeholder, set it manually. Skip this check in local environments.
Run npx agent-reviews --unanswered --expanded
The CLI auto-detects the current branch, finds the associated PR, and authenticates via gh CLI or environment variables. If anything fails (no token, no PR, CLI not installed), it exits with a clear error message.
This shows all unanswered comments (both human and bot) with full detail: complete comment body (no truncation), diff hunk (code context), and all replies. Each comment shows its ID in brackets (e.g., [12345678]).
If zero comments are returned, print "No unanswered comments found" and skip to Phase 2.
For each comment from the expanded output, apply the appropriate evaluation based on whether the author is a bot or a human.
Read the referenced code and determine:
Likely TRUE POSITIVE:
Likely FALSE POSITIVE:
Read the referenced code and the reviewer's comment. Human reviewers are generally more accurate and context-aware than bots. Determine:
Likely ACTIONABLE:
Likely DISCUSSION -- ask the user:
For both bot and human comments:
If TRUE POSITIVE / ACTIONABLE: Fix the code. Track the comment ID and a brief description of the fix.
If FALSE POSITIVE: Do NOT change the code. Track the comment ID and the reason it's not a real bug.
If DISCUSSION: Ask the user to consult the PR author. Apply their decision and track it.
If ALREADY ADDRESSED: Track the comment ID and note why.
If UNCERTAIN: Ask the user. If they say skip, track it as skipped.
Do NOT reply to comments yet. Replies happen after the commit (Step 5).
After evaluating and fixing ALL unanswered comments:
git add -A
git commit -m "fix: address PR review findings
{List of changes made, grouped by reviewer/bot}"
git push
Now that the commit hash exists, reply to every processed comment. The --resolve flag marks the review thread as resolved on GitHub. Use it only when closing the conversation (false positives, discussions concluded, already-addressed, user-skipped), not for fresh fixes that reviewers should still verify.
For each TRUE POSITIVE / ACTIONABLE (we fixed it; leave the thread open so reviewers can verify):
Run npx agent-reviews --reply <comment_id> "Fixed in {hash}. {Brief description of the fix}"
For each FALSE POSITIVE (closing the conversation):
Run npx agent-reviews --reply <comment_id> "Won't fix: {reason}. {Explanation of why this is intentional or not applicable}" --resolve
For each DISCUSSION (after user decision) (the decision concludes the thread):
Run npx agent-reviews --reply <comment_id> "{Outcome}. {Explanation of the decision and any changes made}" --resolve
For each ALREADY ADDRESSED (nothing more to do):
Run npx agent-reviews --reply <comment_id> "Already addressed. {Explanation of when/how this was fixed}" --resolve
For each SKIPPED (user chose not to address it):
Run npx agent-reviews --reply <comment_id> "Skipped per user request" --resolve
Non-threadable comments: If a comment was posted as a PR-level issue comment or review-summary submission (not an inline review comment on a specific line), the CLI cannot post a threaded reply and will print ⊘ Skipped reply: comment is not part of a review thread. That's expected. Record the outcome in the summary and move on; do not retry.
DO NOT start Phase 2 until all replies are posted.
The watcher exits immediately when new comments are found (after a 5s grace period to catch batch posts). This means you run it in a loop: start watcher, process any comments it returns, restart watcher, repeat until the watcher times out with no new comments.
Repeat the following until the watcher exits with no new comments:
6a. Launch the watcher in the background:
Run npx agent-reviews --watch as a background task.
6b. Wait for the background command to complete (default 10 minutes; override with --timeout).
6c. Check the output:
If new comments were found (output contains EXITING WITH NEW COMMENTS):
--detail <id> to read each new comment's full detailIf no new comments (output contains WATCH COMPLETE):
Stop looping and move to the Summary Report.
After both phases complete, provide a summary:
## PR Review Resolution Summary
### Results
- Fixed: X issues
- Already addressed: X
- Won't fix (false positives): X
- Discussion resolved: X
- Skipped per user: X
### By Reviewer/Bot
#### cursor[bot]
- {description} - Fixed in {commit}
- {description} - Won't fix: {reason}
#### @reviewer-name
- {description} - Fixed in {commit}
### Status
All findings addressed. Watch completed.
suggestion blocks often contain ready-to-use fixesnpx claudepluginhub pbakaus/agent-reviews --plugin resolve-reviewsFetches unanswered human PR review comments, evaluates each piece of feedback, applies fixes where appropriate, and replies with the outcome. Useful for clearing PR review bottlenecks.
Reads open GitHub PR review comments, triages by severity, applies code fixes, and drafts replies. Use when addressing PR feedback or code review.
Triages unresolved GitHub PR review comments from bots/humans, deduplicates issues, produces severity-ordered fix plan, resolves ignored threads, and fixes others with subagents before merge.