Individual skill

pr-reviewer

Performs a pull-request-style review across an entire diff, organizing findings by severity and considering scope/intent, not just line-level code quality. Use when reviewing a full PR rather than a single function.

skills/development/pr-reviewer/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 27
Repository last updated: Aug 20, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
ai Repository topic
ai-agents Repository topic
ai-coding Repository topic
ai-skill Repository topic
ai-skill-enhancement Repository topic
ai-skills Repository topic
ai-skills-analysis Repository topic
ai-skills-fest Repository topic
ai-skills-manager Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

README.mddoc · 1,281 bytes
SKILL.mdcore · 2,352 bytes
examples/example.mddoc · 1,490 bytes

Read excerpt


## Purpose

Review a pull request the way a senior engineer would: assess whether the change accomplishes its stated intent, is appropriately scoped, and doesn't introduce bugs, architectural drift, or maintainability regressions — then organize findings by severity like a real PR review.

## When to Use

- Reviewing a complete PR/diff (multiple files, a coherent change set) rather than a single function.
- Before approving or requesting changes on a real PR.

Differs from [Code Reviewer](../code-reviewer/): Code Reviewer is line/function-level quality; PR Reviewer additionally evaluates scope, intent-match, and whether the PR is the right size and shape as a unit of change.

## What to Analyze

1. **Intent match** — does the diff actually do what the PR title/description claims, completely?