A pull request review tool examines proposed code changes before they are merged into a shared codebase. It checks code quality, security, tests, project rules, and consistency with AI-tool instructions.

Use it to review a git diff or changed files, report findings by severity, add file-specific comments, and recommend approval or changes.

It helps find problems and rule violations before they reach the main codebase, when they are easier to fix.

pr-reviewer — Skill for Claude Code and Codex 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.

Any agent

npx skills add vanessamarely/ai-playbook-reposito --skill pr-reviewer

Clone the repo

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

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

Your own site

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

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

When invoked 910 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.00044	$0.00910
Opus 5	$0.00022	$0.00455
Sonnet 5	$0.00009	$0.00182
Haiku 4.5	$0.00004	$0.00091

Measured 12d ago against content hash a857a59fab4d, 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/.agents/skills/pr-reviewer/SKILL.md · 128 lines

How it starts

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

Skill: Pull Request Reviewer

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:

../../../AGENTS.md (always — workspace scope and routing rules)
../../../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)

Read the full file on GitHub · 128 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 · 128 lines · 44 tokens per session scan A a857a59fab4d

Subscribe to this mod's changes

pr-reviewer is a skill published in the GitHub repository vanessamarely/ai-playbook-reposito (2 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 910 once invoked, about $0.0002 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

autoreview

Pre-commit/ship code review: Codex default; optional Claude or Pi.

openclaw/clawhub · 20 tokens

omh-code-review

This is a Hermes-native code-review workflow skill.

rlaope/oh-my-hermes · 46 tokens

revdiff-plan

Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…

umputun/revdiff · 84 tokens

code-reviewer

Code review specialist focused on patterns, bugs, security, and performance.

RightNow-AI/openfang · 17 tokens

full-repo-review

Comprehensive four-wave review of all repo source files, producing a prioritized issue backlog.

notque/vexjoy-agent · 22 tokens

agent-teams-simplify-and-harden

Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…

LeoYeAI/openclaw-master-skills · 115 tokens