pr-review

pr-review is a skill for Claude Code from rp1-run/rp1. It costs 25 tokens per session (3,139 once invoked), scanned A, original, Apache-2.0.

A pull request review workflow that analyses proposed code changes in stages and can work with local checks or CI/CD. A pull request is a request to review and merge changes into a shared codebase; CI/CD means automated building, testing, and delivery.

In plain words
What is it for?
Use it to review pull requests, analyse their changes, combine findings, and post review comments when appropriate.
Why use it?
Large reviews can repeat the same comments or miss issues when changes are examined all at once. This workflow organises the analysis and avoids duplicate review comments.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions OpenCode.

Part of the rp1-dev plugin — 23 skills, 36 agents shipped together

Good fit Use it to review pull requests, analyse their changes, combine findings, and post review comments when appropriate.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rp1-run/rp1/pr-review
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 rp1-run/rp1 --skill pr-review
Clone the repo
git clone --depth 1 https://github.com/rp1-run/rp1

Made for: Claude Code.

Or install rp1-dev, the plugin that ships this one along with the rest of its 23 skills, 36 agents.

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 pr-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/rp1-run/rp1/pr-review/github.svg)](https://agentmods.dev/skills/rp1-run/rp1/pr-review)
Your own site
<a href="https://agentmods.dev/skills/rp1-run/rp1/pr-review"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/pr-review/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 pr-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/rp1-run/rp1/pr-review"><img src="https://agentmods.dev/badge/skills/rp1-run/rp1/pr-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,139 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.00025 $0.03139
Opus 5 $0.00013 $0.01570
Sonnet 5 $0.00005 $0.00628
Haiku 4.5 $0.00003 $0.00314

Measured 4d ago against content hash 2e8eff374996, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

pr-review 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 4d 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/dev/skills/pr-review/SKILL.md · 316 lines

How it starts

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

PR Review Orchestrator

§ROLE: Map-reduce PR review orchestrator. 6 phases, local + CI modes, comment deduplication.

§CTX: Use the pre-resolved projectRoot, kbRoot, and workRoot values from the generated Workflow Bootstrap section. Do not hardcode .rp1/work/ or .rp1/context/ paths.

§GUARDRAILS

  • Never create git worktrees under .rp1/work/ or anywhere inside the target project's .rp1/ directory.
  • If a separate checkout is absolutely required during review, use a temporary path outside the project artifact tree.

References

File Purpose When to Load
references/link-artifacts.md Reusable external link artifact registration pattern and PR review binding During finalization phase (after P4 reporting)
references/analysis-phases.md P0.5 visual gen, P1 splitting, P2 analysis, P3 synthesis, P4 reporting, P5 comment posting After P0 resolves target and intent

STATE-MACHINE

stateDiagram-v2
    [*] --> reviewing
    reviewing --> posting : analysis_complete
    posting --> [*] : done

On each phase transition, report via:

rp1 agent-tools emit \
  --workflow pr-review \
  --type status_change \
  --run-id {RUN_ID} \
  --step {CURRENT_STATE} \
  --data '{"status": "running"}'
  • RUN_ID comes from the generated Workflow Bootstrap section
  • Derive RUN_NAME from the resolved PR context: use "PR #{pr_number}" when a PR number is available, otherwise use "PR: {branch_name}" as fallback
  • On the first emit only, include --name "{RUN_NAME}" to label the run

On session start, emit the status change:

rp1 agent-tools emit \
  --workflow pr-review \
  --type status_change \
  --run-id {RUN_ID} \
  --name "{RUN_NAME}" \
  --step reviewing \
  --data '{"status": "running"}'

State Progression Protocol:

  1. Report each --step with --data '{"status": "running"}' when you enter that state
  2. For non-terminal states: move to the NEXT state when done (entering the next state implies the previous completed)
  3. For terminal states (those with → [*] transitions): report with --data '{"status": "completed"}' and --close-run when the step's work finishes
  4. On error, transition to the appropriate failure state in the graph

Read the full file on GitHub · 316 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 4d ago First seen · 316 lines · 25 tokens per session scan A 2e8eff374996

Subscribe to this mod's changes

pr-review is a skill published in the GitHub repository rp1-run/rp1 (38 stars, last pushed 5d ago), licensed Apache-2.0. It adds 25 tokens to every session and 3,139 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-09-07.

Related

Other skills, from other repositories