Review PR

Review a pull request for correctness, architecture, security, and test coverage. Use when the user names a PR number to review.

44 stars 5 forksGit & Code Review Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add smartwhale8/claude-playbook

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add smartwhale8/claude-playbook --skill review-pr
Manual install
git clone --depth 1 https://github.com/smartwhale8/claude-playbook.git /tmp/claude-playbook
mkdir -p ~/.claude/skills
cp -r /tmp/claude-playbook/.claude/skills/review-pr ~/.claude/skills/review-pr

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Review pull request $ARGUMENTS

## The pull request

!`gh pr view $ARGUMENTS 2>&1 || echo "Could not read PR $ARGUMENTS."`

## The diff

!`gh pr diff $ARGUMENTS 2>&1 | head -1500 || true`

## What to check

1. **Intent.** What is this pull request for? Does the diff do that, and only that?

2. **Correctness.** Trace the changed paths. Unhandled edge cases, off-by-one errors, null and undefined paths, race conditions, error paths that cannot be reached.

3. **Fit.** Does the change follow the patterns already in this codebase? Read the neighbouring files rather than assuming. Name any duplication with the path to the original. Are new dependencies justified?

4. **Security.** Input validation at the boundary, parameterized queries, escaped output, authorization checks on new endpoints, no secrets in the diff.

5. **Tests.** Is each new behaviour covered? Does a bug fix carry a regression test? Are the edge cases tested, or only the happy path?

6. **CI.** Check `gh pr checks $ARGUMENTS`. Do not approve over a red build.

## Output

Open with the verdict: approve, approve with comments, or request changes.

Then the findings, ordered by severity. Each one names the file and line, states the problem, and gives the change that resolves it.

Say plainly what you did not check, for example a subsystem you could not reach or a test you could not run. A review that hides its gaps is worse than a short one.
Read the full skill on GitHub

Details

Skill name
review-pr
Path
.claude/skills/review-pr/SKILL.md
License
MIT
Repo updated
20 September 2026

FAQ

What does the Review PR skill do?

Review a pull request for correctness, architecture, security, and test coverage. Use when the user names a PR number to review.

How do I install the Review PR skill?

Claude Code plugin: /plugin marketplace add smartwhale8/claude-playbook. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Review PR popular?

It lives in smartwhale8/claude-playbook, which has 44 GitHub stars and 5 forks.

Related skills

Fix Issue

44

smartwhale8/claude-playbook

Resolve a GitHub issue end to end, from reading the issue through to opening a pull request. Use when the user names an issue number to fix.

Git & Code Review

Plan Feature

44

smartwhale8/claude-playbook

Turn a rough feature idea into a written specification by interviewing the user first. Use when the user describes something substantial they want built and the approach is not yet settled.

Other

Review

44

smartwhale8/claude-playbook

Review uncommitted changes against the project rules before committing. Use when the user asks for a review of their working tree, asks whether changes are ready to commit, or says they are about to commit.

Other

Regel Check

51

neubauerwilli/gta6-skill

Der Regel-Check. Prüft jeden Clip gegen die Regeln der Kampagne (Länge, Wasserzeichen, Pflicht-Tags, Erwähnung, Plattform, Frist), bevor er rausgeht. Nutze ihn immer vor dem Posten, oder wenn der Nutzer sagt "prüf den Clip", "darf ich das posten", "Regeln checken" oder "ist der Clip okay".

Git & Code Review

Git Workflow

43

jefflester/claude-skills-supercharged

Git workflow best practices including commit messages, branching strategies, pull requests, and collaboration patterns. Use when working with Git version control.

Git & Code Review

Weekly Changelog

49

hw-native-sys/simpler

Summarize user-facing changes merged in the current Friday-anchored week (most recent Friday up through yesterday) in the simpler repo into a markdown changelog with before/after code examples. Also emits a full all-PR inventory (WEEKLY_ALL_PRS) and Chinese (_zh) translations of both docs. Use when the user asks for a weekly changelog, weekly summary, or weekly external changes report.

Git & Code Review102

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.