agentmods.dev

review-pr

review-pr is a skill for Claude Code, Codex from spencerpauly/skills-repo. It costs 50 tokens per session (478 once invoked), scanned A, original, MIT.

Instructions for reviewing a pull request as a senior engineer, focusing on bugs, risks, missing tests, and edge cases.

In plain words
What is it for?
Use them when reviewing a pull request or code diff, including one supplied as a GitHub link.
Why use it?
They provide a consistent way to judge whether a proposed code change is safe to merge instead of focusing mainly on style.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

not rated 27repo +1 4mo ago A scan 50 tokens original MIT

Good fit Use them when reviewing a pull request or code diff, including one supplied as a GitHub link.

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

Made for: Claude Code, Codex.

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/spencerpauly/skills-repo/review-pr/github.svg)](https://agentmods.dev/skills/spencerpauly/skills-repo/review-pr)
Your own site
<a href="https://agentmods.dev/skills/spencerpauly/skills-repo/review-pr"><img src="https://agentmods.dev/badge/skills/spencerpauly/skills-repo/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/spencerpauly/skills-repo/review-pr"><img src="https://agentmods.dev/badge/skills/spencerpauly/skills-repo/review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 478 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.00050 $0.00478
Opus 5.5 $0.00020 $0.00191
Sonnet 5.5 $0.00010 $0.00096
Haiku 4.5 $0.00005 $0.00048

Measured 2mo ago against content hash 92620487ff06, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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.

skills/review-pr/SKILL.md · 56 lines

What it actually says

Review PR

Read a diff the way a thoughtful senior engineer would. Optimize for catching bugs and missing tests, not for nitpicks.

When to use

  • User pastes a GitHub PR URL.
  • User says "review this PR", "what do you think of this diff", "ship-check this".

Steps

  1. Fetch the diff. If a URL was given, run gh pr diff <number> (or gh pr view <number> --json files,title,body). If it's a local branch, git diff main...HEAD.

  2. Read the description first. What is this PR trying to accomplish? Hold that intent in mind for the rest of the review.

  3. Walk the diff in this order:

    1. New files / new entry points (highest risk).
    2. Modified business logic.
    3. Tests.
    4. Configuration, dependencies, infra.

  4. For each substantive change, check the checklist in references/checklist.md.

  5. Write the review in this shape:

    ## Summary
<one paragraph: what changed, what it's trying to do>

## Must-fix
- [ ] <hard bugs, missing error handling, security issues>

## Should-fix
- [ ] <missing tests, brittle code, unclear intent>

## Nits
- [ ] <style, naming, suggestions — keep these short>

## Questions
- <things you genuinely don't understand>

  6. Default posture: approve unless there's a Must-fix. Senior reviewers unblock; they don't gatekeep.

Don't

  • Don't comment on formatting if the repo has a formatter — that's the linter's job.
  • Don't suggest renames unless the existing name is genuinely misleading.
  • Don't ask the author to "consider" something — either it's a Must-fix, a Should-fix, or it's not in the review.
Files

What ships with it

1 file 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. 2mo ago First seen · 56 lines · 50 tokens per session scan A 92620487ff06

Subscribe to this mod's changes

review-pr is a skill published in the GitHub repository spencerpauly/skills-repo (27 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 478 once invoked, about $0.0002 per session on Opus 5.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-30.

Code review
Related

review-pr compared with skills from other repositories

review-pr next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
review-prspencerpauly/skills-repoSkill274mo agoMITA50Claude Code, Codex
autoreviewopenclaw/clawhubSkill9.6ktodayMITA17Claude Code, Codex
agent-teams-simplify-and-hardenLeoYeAI/openclaw-master-skillsSkill2.2k7d agoMITA115Claude Code, Codex
revdiff-planumputun/revdiffSkill956todayMITA84Claude Code
re0-mergeLilMGenius/paperthinSkill1.4k2d agoMITA51Claude Code, Codex
explore-unknownsdzhng/skillsSkill1.5kyesterdayMITA162Claude Code, Codex
asplos-writing-stylebrycewang-stanford/Awesome-Journal-SkillsSkill1.4k1mo agoMITA65Claude Code