review-pr

review-pr is a skill for Claude Code, Codex from tirth8205/code-review-graph. It costs 27 tokens per session (574 once invoked), scanned A, original, MIT.

A code-review guide for examining a pull request or branch difference with full structural context. A pull request is a proposed set of changes for others to review before merging.

In plain words
What is it for?
It is for reviewing all changes in a pull request or branch, measuring their impact, examining important files and functions, identifying high-risk areas, and producing a structured review.
Why use it?
It shows not only what changed but also the wider code that may be affected, helping reviewers find risks across the whole proposal.

Skill for Claude CodeCodex

About the project

code-review-graph is a local-first code intelligence graph that builds a persistent structural map of a codebase and supplies relevant context to AI coding tools through MCP and a CLI. It is used for code review and large-repository workflows, with catalogue add-ons providing integrations and instructions for operating it.

tirth8205/code-review-graph · 31,151 stars · on GitHub

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/tirth8205/code-review-graph/review-pr
Any agent
npx skills add tirth8205/code-review-graph --skill review-pr
Clone the repo
git clone --depth 1 https://github.com/tirth8205/code-review-graph

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.

agentmods badge for review-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/tirth8205/code-review-graph/review-pr.svg)](https://agentmods.dev/skills/tirth8205/code-review-graph/review-pr)
Your own site
<a href="https://agentmods.dev/skills/tirth8205/code-review-graph/review-pr"><img src="https://agentmods.dev/badge/skills/tirth8205/code-review-graph/review-pr.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 574 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.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00574
Opus 5 $0.00014 $0.00287
Sonnet 5 $0.00005 $0.00115
Haiku 4.5 $0.00003 $0.00057

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

How it starts

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

Review PR

Perform a comprehensive code review of a pull request or branch diff using the knowledge graph.

Token optimization: Before starting, call get_docs_section_tool(section_name="review-pr") for the optimized workflow. Never include full files unless explicitly asked.

Steps

  1. Identify the changes for the PR:

    • If a PR number or branch is provided, use git diff main...<branch> to get changed files
    • Otherwise auto-detect from the current branch vs main/master
  2. Update the graph by calling build_or_update_graph_tool(base="main") to ensure the graph reflects the current state.

  3. Get the full review context by calling get_review_context_tool(base="main"):

    • This uses main (or the specified base branch) as the diff base
    • Returns all changed files across all commits in the PR
  4. Analyze impact by calling get_impact_radius_tool(base="main"):

    • Review the blast radius across the entire PR
    • Identify high-risk areas (widely depended-upon code)
  5. Deep-dive each changed file:

    • Read the full source of files with significant changes
    • Use query_graph_tool(pattern="callers_of", target=<func>) for high-risk functions
    • Use query_graph_tool(pattern="tests_for", target=<func>) to verify test coverage
    • Check for breaking changes in public APIs
  6. Generate structured review output:

    ## PR Review: <title>
    
    ### Summary
    <1-3 sentence overview>
    
    ### Risk Assessment
    - **Overall risk**: Low / Medium / High
    - **Blast radius**: X files, Y functions impacted
    - **Test coverage**: N changed functions covered / M total
    
    ### File-by-File Review
    #### <file_path>
    - Changes: <description>
    - Impact: <who depends on this>
    - Issues: <bugs, style, concerns>
    
    ### Missing Tests
    - <function_name> in <file> - no test coverage found
    
    ### Recommendations
    1. <actionable suggestion>
    2. <actionable suggestion>
    

Tips

  • For large PRs, focus on the highest-impact files first (most dependents)
  • Use semantic_search_nodes_tool to find related code the PR might have missed
  • Check if renamed/moved functions have updated all callers

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

  1. 5d ago First seen · 67 lines · 27 tokens per session scan A d48249a140cc

Subscribe to this mod's changes

review-pr is a skill published in the GitHub repository tirth8205/code-review-graph (31,151 stars, last pushed 8d ago), licensed MIT. It adds 27 tokens to every session and 574 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-30.

Related

Other skills, from other repositories

rulesync

Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.

dyoshikawa/rulesync · 64 tokens

autoprompt

Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.

Spielewoy/autoprompt-skill · 56 tokens

loop

Full execution protocol for MODE: LOOP — the compound-engineering loop: brainstorm → plan → build → review → improve, iterating under defense-in-depth stop conditions with generator/critic separation, durable resumable state, and mandatory compounding learning capture. Loaded on demand by the architect when the loop…

ZaxbyHub/opencode-swarm · 72 tokens

restore-internals-seams-in-finally-blocks-after-each-test

When delegating a task affected by this skill, include.

ZaxbyHub/opencode-swarm · 26 tokens

loongsuite-pilot-insight

基于 LoongSuite Pilot / AI Coding Agent 日志生成事件洞察、组织洞察、数据质量、研发效能和 AI Native 使用类 SLS 报表时使用;包含 AI Coding 事件表语义,以及团队报表可选的部门维表、deptuser 组织关系、指标口径和公共 CTE,通常与 sls-dashboard-builder 一起使用。.

alibaba/loongsuite-pilot · 91 tokens

map-fast

Minimal workflow for small, low-risk changes — no planning, no learning.

azalio/map-framework · 17 tokens