pr-review

Reviews pull requests by running them in a git worktree and auditing against a fixed checklist.

1|Updated Nov 25, 2021
One-click install
npx skills add https://github.com/rstagi/dotfile --skill pr-review-rstagi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/rstagi/dotfile/tree/main/.claude/skills/pr-review
Command: npx skills add https://github.com/rstagi/dotfile --skill pr-review-rstagi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Diff-only reviews miss whether code actually builds, runs, and behaves as claimed. This Skill checks out a pull request into an isolated git worktree, runs the project's build and tests, and then audits the change across a fixed set of review lenses so findings are grounded in real behavior. ## Core Features & Use Cases - Run-before-review workflow: Checks out the PR with gh pr checkout or a detached worktree, installs dependencies, runs the test suite, and exercises the changed code path before judging it. - Fixed audit lenses: Evaluates AI slop, obvious bugs, test quality, code and file structure, implementation correctness, docs consistency, and whether the PR should be split into a stack. - Headless mode: Supports a --headless flag for automated orchestration that posts the full report as a PR comment via gh pr comment without interactive prompts. - Use Case: A teammate asks you to review PR #123 before merge. The Skill checks it out, runs the suite, finds a broken error path the diff hid, and reports findings with file:line references ordered by severity. ## Quick Start Ask the assistant to review pull request number 123 and it will check out the branch, run it, and produce a structured review report.

Frequently Asked Questions about pr-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a GitHub pull request by actually running the code?

Check out the PR into a separate git worktree with gh pr checkout and git worktree add, then install dependencies, run the test suite, and exercise the changed code path. This Skill automates that flow and reports findings with file and line references.

What should a thorough pull request review checklist include?

A thorough review covers AI slop, obvious bugs and wrong behavior, test quality, code and file structure, implementation correctness, and docs consistency. This Skill applies exactly those lenses and separates must-fix issues from nice-to-haves.

Can I run an automated PR review without interactive prompts?

Yes, the headless mode skips gh pr checkout, fetches the PR head into a detached worktree, runs the full review, and posts the report as a PR comment via gh pr comment. It never pauses to ask questions or mutates the original checkout.

Why use a git worktree instead of switching branches for review?

A worktree isolates the review build from your working tree, so uncommitted changes and current branch state stay untouched. The detached worktree variant also avoids branch-already-checked-out errors when other worktrees exist.

When should a large pull request be split into a stack?

Split when a PR exceeds roughly 800 changed lines, contains two or more independently reviewable units, or mixes mechanical churn with behavioral change. The Skill proposes an ordered stack of PRs with titles, bases, and paths but never executes the split.