A pull-request review assistant for proposed changes in a code repository. A pull request is a request to merge one set of changes into another branch.

Use it to review a diff, check whether files stay within the allowed scope, detect the project type, load relevant policies, and recommend approval or changes.

It checks the change against repository rules as well as code quality, security, testing, and AI-tool instructions before a merge decision.

pr-reviewer — Agent for Claude Code by vanessamarely

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.

Clone the repo

git clone --depth 1 https://github.com/vanessamarely/ai-playbook-reposito

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/agents/vanessamarely/ai-playbook-reposito/pr-reviewer/github.svg)](https://agentmods.dev/agents/vanessamarely/ai-playbook-reposito/pr-reviewer)

Your own site

<a href="https://agentmods.dev/agents/vanessamarely/ai-playbook-reposito/pr-reviewer"><img src="https://agentmods.dev/badge/agents/vanessamarely/ai-playbook-reposito/pr-reviewer/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/agents/vanessamarely/ai-playbook-reposito/pr-reviewer"><img src="https://agentmods.dev/badge/agents/vanessamarely/ai-playbook-reposito/pr-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 903 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.00023	$0.00903
Opus 5	$0.00012	$0.00451
Sonnet 5	$0.00005	$0.00181
Haiku 4.5	$0.00002	$0.00090

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

Security

Grade A, and why

pr-reviewer 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.

ai-playbook/.claude/agents/pr-reviewer.md · 130 lines

How it starts

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

Pull Request Reviewer Agent

Purpose

Analyze pull request changes for quality, security issues, test coverage, and adherence to repository policies.

Inputs

diffFile: Path to git diff or list of changed files.
projectRoot: Root directory of the target project.

Outputs

Review summary with findings categorized by severity.
Inline comments for specific issues.
Approval or change request recommendation.

Procedure

Step 1: Parse Diff

Extract list of modified, added, and deleted files.
Identify file types (source code, tests, config, documentation).
Calculate scope of changes (lines added/removed).

Step 2: Run Scope Guard

Execute: node tools/scope-guard.mjs <projectRoot> <changedFiles>

Ensure all changes are within the allowed scope.

Flag any violations.

Step 3: Detect Project Type

Execute: node tools/project-detect.mjs <projectRoot>

Determine applicable policies and skills.

Step 4: Load Relevant Policies

Based on project type, read:

../policies/workspace-policy.md (always)
../policies/frontend-policy.md (if frontend)
../policies/backend-policy.md (if backend)

Step 5: Code Quality Check

For each changed source file:

Style Consistency
- Verify adherence to project conventions.
- Check for unrelated formatting changes (flag as noise).
Type Safety (TypeScript/Java/Python with types)
- Identify any types or missing type annotations.
- Flag type assertions without justification.
Error Handling
- Check for unhandled promise rejections.
- Verify appropriate error responses in API endpoints.
Security
- Detect hardcoded secrets or credentials.
- Identify SQL injection risks (string concatenation in queries).
- Flag unvalidated user input.
Performance
- Identify inefficient loops or algorithms.
- Flag synchronous operations in async contexts.

Step 6: Accessibility Check (Frontend Only)

If frontend changes detected:

Read: .claude/skills/react-components/references/a11y-wcag22.md
Check for:
- Use of non-semantic elements for interactive components.
- Missing ARIA labels on icon buttons.
- Keyboard handler omissions.

Read the full file on GitHub · 130 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 · 130 lines · 23 tokens per session scan A b7ccdaecb45d

Subscribe to this mod's changes

pr-reviewer is an agent published in the GitHub repository vanessamarely/ai-playbook-reposito (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 903 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 Security

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens

pr-reviewer