pr-review

Reviews GitHub pull requests through progressive, layered code analysis.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/nvie/skills --skill pr-review-nvie
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/nvie/skills/tree/main/skills/pr-review
Command: npx skills add https://github.com/nvie/skills --skill pr-review-nvie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing large or multi-repo pull requests is time-consuming, and dumping every nit at once overwhelms both reviewer and author. This Skill guides a senior engineer through a PR one abstraction layer at a time, building an accurate mental model first and surfacing only genuinely interesting findings and questions. ## Core Features & Use Cases - Layered review flow: Starts with a high-level summary of what the change does and how, then descends into concepts/naming, implementation, and deep code-quality audit only when asked. - Multi-PR support: Treats a frontend + backend PR pair as one logical change, focusing on the contract between them. - Comment-ready output: Turns numbered findings into ready-to-paste GitHub inline comments with clickable deep links to exact diff lines. - Use Case: You receive a backend PR and its frontend counterpart. Run the Skill with both URLs to get a concise mental model, 5-10 sharp questions for the author, and then drill into implementation details only where it matters. ## Quick Start Ask the assistant to review these pull requests by running /pr-review followed by one or more GitHub PR URLs.

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 with AI assistance?▼

Run /pr-review with one or more GitHub PR URLs. The review starts with a high-level summary of what the change does and how, then offers a handful of sharp questions and observations before drilling deeper only when you ask.

How to review frontend and backend PRs together as one change?▼

Pass both PR URLs to the same review invocation. The Skill treats them as one logical change and focuses on the contract between the parts, such as a shared type, protocol bump, or API the other side consumes.

Can I review a PR using a local checkout instead of the GitHub API?▼

Yes. The Skill prefers local code when a worktree with the PR branch is available, letting it read full files, run tests, and try theories. It falls back to gh pr diff and gh pr view when no local checkout exists.

How do I turn a review finding into an inline GitHub comment?▼

Reply with the finding's number, and the Skill emits a clickable deep link to the exact diff line plus a ready-to-paste comment body in GitHub-flavored Markdown, optionally with a suggestion block for concrete code changes.

Does this code review repeat comments already raised on the PR?▼

No. It reads the PR's existing comments and review threads first and skips points already under discussion, only following up on existing threads when they match the current altitude of the review.