review-pr
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:
- 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.
More from tobihagemann/turbo
find-dead-code
Find dead code using parallel subagent analysis and optional CLI tools, treating code only referenced from tests as dead. Use when the user asks to \"find dead code\", \"find unused code\", \"find unused exports\", \"find unreferenced functions\", \"clean up dead code\", or \"what code is unused\". Analysis-only — does not modify or delete code.
30simplify-code
Run a multi-agent review of changed files for reuse, quality, efficiency, and clarity issues followed by automated fixes. Use when the user asks to \"simplify code\", \"review changed code\", \"check for code reuse\", \"review code quality\", \"review efficiency\", \"simplify changes\", \"clean up code\", \"refactor changes\", or \"run simplify\".
23smoke-test
Launch the app and hands-on verify that it works by interacting with it. Use when the user asks to \"smoke test\", \"test it manually\", \"verify it works\", \"try it out\", \"run a smoke test\", \"check it in the browser\", or \"does it actually work\". Not for unit/integration tests.
22finalize
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to \"finalize implementation\", \"finalize changes\", \"wrap up implementation\", \"finish up\", \"ready to commit\", or \"run QA workflow\".
22self-improve
Extract lessons from the current session and route them to the appropriate knowledge layer (project AGENTS.md, auto memory, existing skills, or new skills). Use when the user asks to \"self-improve\", \"distill this session\", \"save learnings\", \"update CLAUDE.md with what we learned\", \"capture session insights\", \"remember this for next time\", \"extract lessons\", \"update skills from session\", or \"what did we learn\".
22evaluate-findings
Critically assess external feedback (code reviews, AI reviewers, PR comments) and decide which suggestions to apply using adversarial verification. Use when the user asks to \"evaluate findings\", \"assess review comments\", \"triage review feedback\", \"evaluate review output\", or \"filter false positives\".
22