review-pr

review-pr is a skill for Claude Code from n24q02m/claude-plugins. It costs 28 tokens per session (956 once invoked), scanned A, original, Apache-2.0.

A pull-request review that examines every commit and the complete difference between a development branch and its base branch.

In plain words
What is it for?
Use it to check whether a branch is ready to submit as a pull request, review commits, and verify Conventional Commits messages such as feat(scope): description.
Why use it?
It helps catch breaking changes, unclear commit history, and issues that a quick review of only the latest local edits can miss.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Part of the better-code-review-graph plugin — 6 skills shipped together

Good fit Use it to check whether a branch is ready to submit as a pull request, review commits, and verify Conventional Commits messages such as feat(scope): description.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/n24q02m/claude-plugins/review-pr
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add n24q02m/claude-plugins --skill review-pr
Clone the repo
git clone --depth 1 https://github.com/n24q02m/claude-plugins

Made for: Claude Code.

Or install better-code-review-graph, the plugin that ships this one along with the rest of its 6 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for review-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/n24q02m/claude-plugins/review-pr/github.svg)](https://agentmods.dev/skills/n24q02m/claude-plugins/review-pr)
Your own site
<a href="https://agentmods.dev/skills/n24q02m/claude-plugins/review-pr"><img src="https://agentmods.dev/badge/skills/n24q02m/claude-plugins/review-pr/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for review-pr

Your own site · 80×15
<a href="https://agentmods.dev/skills/n24q02m/claude-plugins/review-pr"><img src="https://agentmods.dev/badge/skills/n24q02m/claude-plugins/review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 956 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00956
Opus 5 $0.00014 $0.00478
Sonnet 5 $0.00006 $0.00191
Haiku 4.5 $0.00003 $0.00096

Measured 9d ago against content hash e965c23a5ae8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

review-pr scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

plugins/better-code-review-graph/skills/review-pr/SKILL.md · 96 lines

How it starts

The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review PR

Comprehensive code review of a pull request or branch diff against its base. Unlike review-delta (quick review of uncommitted local changes), this reviews ALL commits in a branch for PR submission readiness.

Command surface: run the local CLI through the coding harness shell. Examples use the installed better-code-review-graph command; from a source checkout, prefix it with uv run. No MCP mapping is required. Use better-code-review-graph review --help for the command reference. Never include full files unless explicitly asked.

Steps

  1. Identify the changes for the PR:

    • If a PR number or branch is provided, use git diff main...<branch> to get changed files
    • Otherwise auto-detect from the current branch vs main/master
  2. Update the graph with better-code-review-graph graph build --base main --repo-root "<path>" so it reflects the current branch.

  3. Commit-by-commit analysis (for PRs with >3 commits):

    • git log --oneline main..HEAD to list all commits
    • Group related commits by area (feature, fix, refactor, test, docs)
    • Verify each commit message follows Conventional Commits (type(scope): description)
    • Flag commits that mix unrelated changes
  4. Get the full review context with better-code-review-graph review context --base main --repo-root "<path>":

    • Returns all changed files across all commits in the PR
    • Includes impacted nodes and blast radius
  5. Analyze impact with better-code-review-graph query impact --base main --repo-root "<path>":

    • Review the blast radius across the entire PR
    • Identify high-risk areas (widely depended-upon code)
  6. Breaking change detection for public APIs:

    • Identify exported/public functions, classes, types that changed
    • Check for: removed parameters, changed return types, renamed exports, removed functions
    • Use better-code-review-graph query query --pattern callers_of --target "<function>" --repo-root "<path>" to find all consumers
    • Flag any change where callers outside the PR would break

Read the full file on GitHub · 96 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 96 lines · 28 tokens per session scan A e965c23a5ae8

Subscribe to this mod's changes

review-pr is a skill published in the GitHub repository n24q02m/claude-plugins (4 stars, last pushed today), licensed Apache-2.0. It adds 28 tokens to every session and 956 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

pr-triage

4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…

FlorianBruniaux/claude-code-plugins · 86 tokens

validate-changes

Evaluate staged changes using LLM-as-a-Judge before committing.

FlorianBruniaux/claude-code-plugins · 16 tokens

issue-analyzing

Use this skill when the user asks to analyze a specific GitHub issue, understand what area of code an issue affects, assess an issue's scope, or research the code context around an issue — example triggers like "analyze issue.

shopwareLabs/ai-coding-tools · 51 tokens

pr-checklist

Generate a PR checklist based on changes.

sunnypatneedi/claude-starter-kit · 11 tokens

babysit

Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

thedotmack/claude-mem · 44 tokens

code-review

Review the current diff, or a PR number/branch/path target, for correctness bugs and reuse/simplification/efficiency cleanups at the given effort level (low/medium: fewer, high-confidence findings; high→max: broader coverage, may include uncertain findings; ultra: deep multi-agent review in the cloud); with no level…

asgeirtj/system_prompts_leaks · 0 tokens