Claude Skill

review-pr

Review a pull request by fetching PR comments, running a comprehensive code review, evaluating findings, and dispatching to implementation. Use when the user asks to "review PR", "review pull request", "review this PR", "check PR before merging", or "full PR review".

LLM Mart · 0 points · 17 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download tobihagemann-turbo-codex_skills_review-pr-b903a85.zip · 0 KB

tobihagemann/turbo 403 31 forks MIT Updated 1d ago

Part of tobihagemann/turbo — 147 skills

Install

skills CLI npx skills add https://github.com/tobihagemann/turbo/tree/main/codex/skills/review-pr

Claude Code claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install tobihagemann-turbo@llmmart

Git git clone https://github.com/tobihagemann/turbo.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole tobihagemann/turbo collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Review PR

Fetch PR context, run a comprehensive code review, evaluate findings, and dispatch accepted findings to implementation.

Task Tracking

At the start, use update_plan to track each step, restating any remaining steps of a parent workflow alongside them:

Run $fetch-pr-comments skill
Resolve base branch
Run $review-code skill
Run $evaluate-findings skill
Run $resolve-findings skill

Step 1: Run `$fetch-pr-comments` Skill

Run the $fetch-pr-comments skill to get unresolved review comments.

Step 2: Resolve Base Branch

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

Step 3: Run `$review-code` Skill

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.

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.

Files (turbo)

SKILL.md 1.8 KB

---
name: review-pr
description: "Review a pull request by fetching PR comments, running a comprehensive code review, evaluating findings, and dispatching to implementation. Use when the user asks to \"review PR\", \"review pull request\", \"review this PR\", \"check PR before merging\", or \"full PR review\"."
---

# Review PR

Fetch PR context, run a comprehensive code review, evaluate findings, and dispatch accepted findings to implementation.

## Task Tracking

At the start, use `update_plan` to track each step, restating any remaining steps of a parent workflow alongside them:

1. Run `$fetch-pr-comments` skill
2. Resolve 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: Resolve Base Branch

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

## Step 3: Run `$review-code` Skill

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.

## 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.