Skip to content

tobihagemann/turbo / claude/skills/review-pr

review-pr

Verified

Review a pull request: run a full code review of its diff, evaluate findings, and implement them. Use when the user asks to "review PR", "review this PR", or "check PR before merging".

FileKindSize
SKILL.mdskill md1.6 KB
---
name: review-pr
description: "Review a pull request: run a full code review of its diff, evaluate findings, and implement them. Use when the user asks to \"review PR\", \"review this PR\", or \"check PR before merging\"."
---

# Review PR

Run a comprehensive code review of the PR's diff, evaluate findings, and dispatch accepted findings to implementation.

## Task Tracking

At the start, use `TaskCreate` to create a task for each step:

1. Resolve base branch
2. Run `/review-code` skill
3. Run `/evaluate-findings` skill
4. Run `/implement-findings` skill

## Step 1: Resolve Base Branch

Detect the PR's base branch and the issues it closes via `gh pr view --json baseRefName,closingIssuesReferences`, then run `git fetch origin <base-branch>` to bring the remote ref up to date.

## Step 2: Run `/review-code` Skill

When the PR closes issues, fetch each by its URL with `gh issue view <url> --json title,body,comments`, issuing the calls together. Together, their text is the governing document.

Run the `/review-code` skill. The diff command is `git diff origin/<base-branch>...HEAD`. Take the base from `origin/`: a local branch of the same name can sit behind the remote, which puts the merge base before an already-merged pull request and pulls merged work into the review as if it were new. Supply the governing document when there is one.

## Step 3: Run `/evaluate-findings` Skill

Run the `/evaluate-findings` skill on the results from Step 2.

## Step 4: Run `/implement-findings` Skill

If zero actionable findings survive evaluation, report that the code looks clean and stop.

Otherwise, run the `/implement-findings` skill on the accepted findings from Step 3.
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 323kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 323kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 323kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 323kUpdated Claude CodeCodexVerifiedInstall