A code-review command for an open GitHub pull request, which is a proposed set of changes to a project. It checks the request's details and changed code, then gives structured feedback and can optionally post it on GitHub.

Use it to review a pull request by its number or URL, summarize the changes, identify actionable issues with file locations, and choose whether to approve, request changes, or comment.

It gathers the pull request context and organizes checks for bugs, security, performance, code quality, and documentation. This reduces the manual work needed to inspect a change before it is merged.

How lsiyu241-creator/awesome-claude-cookbook configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to lsiyu241-creator/awesome-claude-cookbook. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/lsiyu241-creator/awesome-claude-cookbook/main/.claude/commands/review-pr.md

Clone the repo

git clone --depth 1 https://github.com/lsiyu241-creator/awesome-claude-cookbook

Made for: Claude Code.

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/commands/lsiyu241-creator/awesome-claude-cookbook/review-pr/github.svg)](https://agentmods.dev/commands/lsiyu241-creator/awesome-claude-cookbook/review-pr)

Your own site

<a href="https://agentmods.dev/commands/lsiyu241-creator/awesome-claude-cookbook/review-pr"><img src="https://agentmods.dev/badge/commands/lsiyu241-creator/awesome-claude-cookbook/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/lsiyu241-creator/awesome-claude-cookbook/review-pr"><img src="https://agentmods.dev/badge/commands/lsiyu241-creator/awesome-claude-cookbook/review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 715 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 100% copy Near-identical to another mod 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.1	$0.00013	$0.00715
Opus 5	$0.00006	$0.00358
Sonnet 5	$0.00003	$0.00143
Haiku 4.5	$0.00001	$0.00072

Measured 12d ago against content hash 2e6578f10177, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, 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 12d 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.

Origin

This is a copy

100% identical to review-pr — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/review-pr.md · 120 lines

How it starts

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

Arguments

$ARGUMENTS: The PR number or URL to review

Your task

Review the specified pull request and provide feedback.

Step 1: Checkout the PR

First, checkout the PR using:

gh pr checkout $ARGUMENTS

Step 2: Gather PR context

Get the PR details:

gh pr view $ARGUMENTS
gh pr diff $ARGUMENTS

Step 3: Review the code changes

Use the Task tool with subagent_type: "code-reviewer" to perform a thorough code review of the changes. Pass the diff and changed files to the agent for analysis.

The code-reviewer agent will analyze:

Code quality and best practices
Potential bugs or issues
Security concerns
Performance considerations
Documentation and comments

Step 4: Present the review

After the code review is complete, present the review to the user using this format:

## PR Review

**Recommendation**: APPROVE | REQUEST_CHANGES | COMMENT

### Summary
[1-2 sentence overview of what this PR does]

### Actionable Feedback (N items)
- [ ] `file.py:42` - Description of issue or required change
- [ ] `notebook.ipynb` (in cell with `some_code = ...`) - Description

### Detailed Review

#### Code Quality
[Analysis of code patterns, readability, maintainability]

#### Security
[Any security considerations]

#### Suggestions
[Optional improvements]

#### Positive Notes
[What was done well]

Guidelines:

Use checkboxes for actionable items so authors can track progress
For Jupyter notebooks, reference code snippets instead of cell numbers
Be specific with file:line references where possible

Step 5: Ask about posting the review

Use the AskUserQuestion tool to ask the user:

Whether they want to post this review to GitHub
What review action to take: APPROVE, REQUEST_CHANGES, or COMMENT

Step 6: Post the review (if approved)

If the user confirms, post the review using:

gh pr review $ARGUMENTS --body "YOUR_REVIEW_BODY" --approve|--request-changes|--comment

When posting to GitHub, wrap the Detailed Review section in a collapsible <details> tag to reduce noise:

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

12d ago First seen · 120 lines · 13 tokens per session scan A 2e6578f10177

Subscribe to this mod's changes

review-pr is a command published in the GitHub repository lsiyu241-creator/awesome-claude-cookbook (3 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 715 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to review-pr, differing in 0 lines, and is treated as a copy.

Code review Git and workflow

awesome-claude-cookbook: Command for Claude Code