pr-review

Review GitHub pull requests in isolated worktrees against project specifications.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you review GitHub pull requests deeply and consistently without mixing changes into your main workspace, while checking the diff against project specifications and review rules.

Core Features & Use Cases

  • Isolated PR Review: Creates a detached worktree so you can inspect the pull request safely and independently.
  • Specification Cross-Check: Reads project guidance such as CLAUDE.md, AGENTS.md, docs, and spec files to validate the change against expected behavior.
  • Parallel Analysis and Self-Verification: Can combine a main review with an optional Codex pass, then runs fact-check and scope-check passes before producing the final report.
  • Use Case: Use this Skill when a pull request needs a thorough review that separates must-fix issues from should-fix improvements and identifies both missing implementation and out-of-scope edits.

Quick Start

Use the pr-review skill to inspect a pull request URL or issue number, compare it against the relevant project specs, and return a structured review with prioritized findings.

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 against project specifications?

Reviewing a GitHub pull request against project specifications involves checking the diff in an isolated worktree and validating changes against docs like CLAUDE.md. This process produces actionable findings that separate must-fix issues from out-of-scope edits.

What is the best way to perform a spec-driven code review for a pull request?

A spec-driven code review compares pull request diffs against project rules and documentation. By reading spec files and applying fact-check and scope-check passes, the review identifies missing implementations and separates critical issues from minor improvements.

Can I review a current branch diff without affecting my main workspace?

Yes, reviewing a current branch diff without affecting your main workspace is possible by creating a detached worktree. This isolates the pull request changes, allowing safe and independent inspection without mixing edits into your local environment.

Does isolated worktree code review support parallel analysis passes?

Isolated worktree code review supports parallel analysis by combining a main review with an optional Codex pass. It merges duplicate findings and runs fact-check and scope-check verifications before producing the final structured report.

What limitations does spec-aware pull request review have?

Spec-aware pull request review is limited to same-repository pull requests, current-branch reviews, and specification-driven audits. It requires project guidance files like CLAUDE.md or docs to validate changes and does not support cross-repository pull requests.

How to categorize code review findings by priority during a diff analysis?

Categorizing code review findings by priority involves running fact-check and scope-check passes on the diff analysis. This structured approach separates must-fix issues from should-fix improvements and explicitly flags out-of-scope edits in the final output.