Menu
Review and address PR comments for the current branch's pull request. Fetches review comments, plans fixes, confirms with the user, then implements and pushes.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Take over a stale or abandoned PR. Checks out the work, merges main, deep-reviews the code, addresses all review comments, then re-creates a clean PR crediting the original author.
Fetch a GitHub issue by number, create a branch off latest main, research the codebase, plan the fix, implement with full test coverage and documentation.
Paranoid architect review of a PR. Given a GitHub PR link or number, performs deep code review for bugs, security vulnerabilities, missing tests, undocumented assumptions, and edge cases. Leaves comments on GitHub for the author.
Deep audit of a Rust crate for vulnerabilities, bugs, unfinished work, inconsistencies, duplicate code, and oversights. Works on the current crate or a specified path.
| name | review-pr |
| description | Review and address PR comments for the current branch's pull request. Fetches review comments, plans fixes, confirms with the user, then implements and pushes. |
| disable-model-invocation | true |
| allowed-tools | Bash(gh *), Bash(git *), Bash(cargo *), Read, Edit, Write, Grep, Glob |
| argument-hint | [pr-number (optional, auto-detects from branch)] |
If $ARGUMENTS is provided, use that as the PR number. Otherwise, detect the PR for the current branch:
gh pr list --head $(git branch --show-current) --json number,title,url --jq '.[0]'
If no PR is found, tell the user and stop.
Fetch the full set of review comments (not issue-level comments):
gh api repos/{owner}/{repo}/pulls/{number}/comments
Also fetch the review summaries:
gh api repos/{owner}/{repo}/pulls/{number}/reviews
Deduplicate comments that appear multiple times (bots sometimes post the same finding under different IDs). Group by the actual issue being raised, not by comment ID.
For each unique issue raised in the comments:
Present the plan as a table to the user:
| # | Issue | File:Line | Severity | Status | Planned Fix |
|---|
Wait for user confirmation before proceeding to implementation.
After user confirms:
For each comment addressed, reply on the PR with a short message stating what was fixed and the commit SHA. For false positives or already-resolved items, reply explaining why no change was needed.