A command that reviews a GitHub pull request, which is a proposed set of code changes, and posts structured findings back to GitHub.

Use it to fetch a pull request, analyze its changes, and post review comments or findings, including an optional repository.

It checks the pull request's state and diff before reviewing, so the review accounts for drafts, closed changes, missing diffs, and truncated content.

How Oolab-labs/claude-ide-bridge configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Oolab-labs/claude-ide-bridge. 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/Oolab-labs/claude-ide-bridge/main/.claude/commands/review-pr.md

Clone the repo

git clone --depth 1 https://github.com/Oolab-labs/claude-ide-bridge

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/oolab-labs/claude-ide-bridge/review-pr/github.svg)](https://agentmods.dev/commands/oolab-labs/claude-ide-bridge/review-pr)

Your own site

<a href="https://agentmods.dev/commands/oolab-labs/claude-ide-bridge/review-pr"><img src="https://agentmods.dev/badge/commands/oolab-labs/claude-ide-bridge/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/oolab-labs/claude-ide-bridge/review-pr"><img src="https://agentmods.dev/badge/commands/oolab-labs/claude-ide-bridge/review-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,405 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.

Model	Per session	Once invoked
Fable 5.1	$0.00008	$0.01405
Opus 5	$0.00004	$0.00702
Sonnet 5	$0.00002	$0.00281
Haiku 4.5	$0.00001	$0.00140

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

review-pr — 100% identical, 0 lines differ

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

How it starts

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

GitHub PR Code Review

Review pull request #$1 and post findings back to GitHub as a structured code review.

Repository (optional): $2

Step 1: Fetch the PR and Validate State

Call githubGetPRDiff with prNumber $1. If $2 is provided, pass it as repo.

If the tool returns an error, report it to the user and stop.

After fetching, check these conditions before proceeding:

Closed/merged PR: If state is CLOSED or MERGED, warn the user that the PR is no longer open and ask whether they still want a review. If proceeding, always use COMMENT event (never REQUEST_CHANGES on non-open PRs).
Draft PR: If isDraft is true, inform the user this is a draft PR and ask whether to proceed. The author may not be ready for review.
Diff unavailable: If the diff field starts with "(diff unavailable", inform the user the diff could not be fetched (typically because the head branch was deleted after merge). Stop — inline comments are not possible without a diff. Only a summary review based on metadata can be posted.
Truncated diff: If truncated is true, warn the user that the diff exceeds 256 KB and only a partial review is possible. Note in the review body that the analysis covers the first 256 KB only. Be cautious with inline comments near the end of the visible diff — line numbers may not map correctly.
Incomplete file list: If filesIncomplete is true, warn that not all changed files are listed (GitHub API pagination limit). The review will cover only the files visible in the diff.

Step 2: Assess Review Depth

Check the PR metadata to determine review scale:

Small (< 100 lines changed = additions + deletions): Single-pass review of the entire diff
Medium (100–500 lines): Review file-by-file, examining each changed file in sequence
Large (500+ lines): Launch up to 3 parallel Agent subagents, each reviewing a subset of the changed files. Combine their findings before proceeding.

For large PRs, split files into groups and give each agent the relevant portion of the diff with instructions to find bugs, security issues, error handling gaps, and performance concerns.

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

9d ago First seen · 121 lines · 8 tokens per session scan A 3bfa1304ef7b

Subscribe to this mod's changes

review-pr is a command published in the GitHub repository Oolab-labs/claude-ide-bridge (38 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 1,405 once invoked, about $0.0000 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-30.

Claude Code Code review Git and workflow ai claude developer-tools ide lsp

claude-ide-bridge: Command for Claude Code