A pull-request review workflow that examines the proposed code changes, the surrounding files, and the request details. A pull request is a proposed change set submitted for review before it is merged.

It is for reviewing a pull request’s description, changed files, and full diff, then producing structured feedback.

It helps find correctness, security, performance, maintainability, and testing problems that may be missed by reading only the change summary.

pr-review — Skill for Claude Code and Codex by billbuchanan-code: A pull-request review workflow that examines the proposed code…

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.

agentmods

npx agentmods add skills/billbuchanan-code/claude-code-power-setup/pr-review

Any agent

npx skills add billbuchanan-code/claude-code-power-setup --skill pr-review

Clone the repo

git clone --depth 1 https://github.com/billbuchanan-code/claude-code-power-setup

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/pr-review.svg)](https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/pr-review)

Your own site

<a href="https://agentmods.dev/skills/billbuchanan-code/claude-code-power-setup/pr-review"><img src="https://agentmods.dev/badge/skills/billbuchanan-code/claude-code-power-setup/pr-review.svg" alt="Measured on agentmods" height="20"></a>

Per session 17 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 551 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00017	$0.00551
Opus 5	$0.00009	$0.00275
Sonnet 5	$0.00003	$0.00110
Haiku 4.5	$0.00002	$0.00055

Measured 3d ago against content hash 9554497482bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 3d 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/pr-review/SKILL.md · 61 lines

How it starts

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

PR Review Skill

Review a pull request by analyzing the diff, checking for issues, and providing structured feedback.

Process

Get the PR number from $ARGUMENTS. If no PR number is provided, detect the current branch's PR using gh pr view --json number.
Fetch PR details by running:
- gh pr view <number> for the PR description, title, and metadata
- gh pr diff <number> for the full diff
- gh pr view <number> --json files to get the list of changed files
For each changed file, read the full file using Read to understand the broader context around the changes. Do not review the diff in isolation.
Analyze changes across these dimensions:
- Correctness: Does the code do what it claims? Are there logic errors, off-by-one errors, or missing edge cases?
- Security: Are there injection risks, exposed secrets, missing auth checks, or unsafe operations?
- Performance: Are there N+1 queries, unnecessary allocations, missing indexes, or algorithmic concerns?
- Maintainability: Is the code readable? Are names clear? Is there unnecessary complexity or duplication?
- Test coverage: Were tests added or updated for new behavior? Are edge cases covered?
Check for missing tests: If new functionality was added without corresponding tests, flag it.
Generate a structured review using the output format below.

Output Format

Structure the output as a PR Review with the following sections:

Summary

One paragraph describing what this PR does and its overall quality.

Must Fix

Critical issues that should be resolved before merging. These are bugs, security issues, or correctness problems. List file path and line number for each.

Should Fix

Non-critical issues that would improve the code. These are performance concerns, maintainability improvements, or minor bugs. List file path and line number for each.

Suggestions

Optional improvements — style, naming, alternative approaches. These are nice-to-haves.

Read the full file on GitHub · 61 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.

3d ago First seen · 61 lines · 17 tokens per session scan A 9554497482bc

Subscribe to this mod's changes

pr-review is a skill published in the GitHub repository billbuchanan-code/claude-code-power-setup (2 stars, last pushed 1mo ago), licensed MIT. It adds 17 tokens to every session and 551 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.

Code review

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens