review-pr
This Claude Code skill automates pull request reviews by fetching existing PR comments, detecting the base branch, performing comprehensive code analysis on the diff, evaluating findings for actionability, and dispatching accepted issues to implementation. Use it when reviewing pull requests before merging or when requesting a full PR review assessment.
git clone --depth 1 https://github.com/tobihagemann/turbo /tmp/review-pr && cp -r /tmp/review-pr/claude/skills/review-pr ~/.claude/skills/review-prSKILL.md
# Review PR Fetch PR context, run a comprehensive code review, evaluate findings, and dispatch accepted findings to implementation. ## Task Tracking At the start, use `TaskCreate` to create a task for each step: 1. Run `/fetch-pr-comments` skill 2. Detect base branch 3. Run `/review-code` skill 4. Run `/evaluate-findings` skill 5. Run `/resolve-findings` skill ## Step 1: Run `/fetch-pr-comments` Skill Run the `/fetch-pr-comments` skill to get unresolved review comments. ## Step 2: Detect Base Branch Detect the PR's base branch via `gh pr view --json baseRefName --jq '.baseRefName'`. ## Step 3: Run `/review-code` Skill Run the `/review-code` skill. The diff command is `git diff <base-branch>...HEAD`. ## Step 4: Run `/evaluate-findings` Skill Run the `/evaluate-findings` skill on the combined results from Step 3. Include any unresolved PR comments from Step 1 as additional findings for evaluation. ## Step 5: Run `/resolve-findings` Skill If zero actionable findings survive evaluation, report that the code looks clean and stop. Otherwise, run the `/resolve-findings` skill on the accepted findings from Step 4. ## Rules - If fetching PR comments fails, proceed with code review only.
For each reviewer question on a PR, recall implementation reasoning and compose a raw answer. Use when the user asks to \"answer reviewer questions\", \"draft answers to PR questions\", or \"explain reviewer questions\".
Apply findings by making the suggested code changes. Applies accepted verdicts, escalates ambiguous findings to the user, and offers to note genuine improvements for later. Use when the user asks to \"apply findings\", \"apply fixes\", \"apply suggestions\", \"apply accepted findings\", \"fix the findings\", or \"apply the review results\".
Project-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md. Use when the user asks to \"audit the project\", \"run a full audit\", \"project health check\", \"audit my code\", \"codebase audit\", or \"comprehensive review\".
Shared changelog conventions and formatting rules referenced by $create-changelog and $update-changelog. Not typically invoked directly.
Enforce mirror, reuse, and symmetry principles to keep new code consistent with surrounding code. Use when writing new code in an existing codebase, adding new features, refactoring, or making any code changes.
Run autonomous task execution using the codex CLI. Use when the user asks to \"codex exec\", \"run codex exec\", \"execute a task with codex\", or \"delegate to codex\".
Run AI-powered code review using the codex CLI. Use when the user asks to \"codex review\", \"run codex review\", or \"review a commit with codex\".
Shared commit message rules and technical constraints referenced by $stage-commit and $commit-staged. Not typically invoked directly.