Review Pr Agent Skill
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\".
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/tobihagemann/turbo --skill review-prThe instruction itself
8 sections, as written by the authorReview 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-commentsskill - Detect base branch
- Run
$review-codeskill - Run
$evaluate-findingsskill - Run
$resolve-findingsskill
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.
Other skills for the same job
different authors, same section of the catalogue
Use 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 implementation
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping
Comprehensive GitHub code review with AI-powered swarm coordination
Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.
Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.
Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.
Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.
How to use it
Take tobihagemann/turbo-review-pr from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.