review-delta

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

A focused code-review guide for changes made since the last commit, including the nearby code affected by those changes. A commit is a saved checkpoint in a version-control system.

In plain words
What is it for?
It is for reviewing changed files, checking callers and dependent files, examining inheritance changes, and flagging edits with a wide impact or insufficient test coverage.
Why use it?
It limits the review to the current change and its likely impact, making it easier to spot bugs, missing updates, and test gaps.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit It is for reviewing changed files, checking callers and dependent files, examining inheritance changes, and flagging edits with a wide impact or insufficient test coverage.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tirth8205/code-review-graph/review-delta
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 · 32,264 stars · on GitHub · code-review-graph.com

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 tirth8205/code-review-graph --skill review-delta
Clone the repo
git clone --depth 1 https://github.com/tirth8205/code-review-graph

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.

agentmods badge for review-delta

README.md
[![agentmods](https://agentmods.dev/badge/skills/tirth8205/code-review-graph/review-delta/github.svg)](https://agentmods.dev/skills/tirth8205/code-review-graph/review-delta)
Your own site
<a href="https://agentmods.dev/skills/tirth8205/code-review-graph/review-delta"><img src="https://agentmods.dev/badge/skills/tirth8205/code-review-graph/review-delta/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.

agentmods 80×15 button for review-delta

Your own site · 80×15
<a href="https://agentmods.dev/skills/tirth8205/code-review-graph/review-delta"><img src="https://agentmods.dev/badge/skills/tirth8205/code-review-graph/review-delta.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 291 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. Third-party audits
  • Socket pass 16 Sept 2026
  • Snyk pass 16 Sept 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00024 $0.00291
Opus 5.5 $0.00010 $0.00116
Sonnet 5.5 $0.00005 $0.00058
Haiku 4.5 $0.00002 $0.00029

Measured 1mo ago against content hash 141c520fa4e7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review-delta 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 1mo 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:

skills/review-delta/SKILL.md · 26 lines

What it actually says

Review Delta

Review only the changed code and its blast radius.

Steps

  1. Call get_minimal_context_tool(task="review changes"). If it returns status: not_ready, call build_or_update_graph_tool() and continue.
  2. Call detect_changes_tool(detail_level="minimal") for risk-scored changed functions, test gaps and affected flows. Changes come from git diff against HEAD~1; if the argument names a file, pass it in changed_files.
  3. Call get_review_context_tool(detail_level="minimal") when you need source snippets for the changed areas and review_guidance (untested functions, wide blast radius, inheritance changes).
  4. For each untested high-risk function, confirm with query_graph_tool(pattern="tests_for", target="<function>").
  5. Use detail_level="standard" only for a high-risk item the minimal output leaves unclear. Do not load whole files unless a snippet is not enough.

Report

  • Summary: one line
  • Risk: low, medium or high, from the blast radius
  • Issues: bugs, missing tests, style
  • Blast radius: impacted files and functions
  • Recommendations
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. 1mo ago Changed · -21 lines 141c520fa4e7
  2. 1mo ago First seen · 47 lines · 24 tokens per session scan A 509f8bf787a2

Subscribe to this mod's changes

review-delta is a skill published in the GitHub repository tirth8205/code-review-graph (32,264 stars, last pushed 4d ago), licensed MIT. It adds 24 tokens to every session and 291 once invoked, about $0.0001 per session on Opus 5.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

work-unit-commits

Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.

Gentleman-Programming/gentle-ai · 33 tokens

gentle-ai-work-unit-commits

Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.

Gentleman-Programming/gentle-pi · 36 tokens

ring:generating-pr-descriptions

Generating pull request descriptions from git branch changes with automatic title generation, change-type detection, and smart analysis. Uses branch-only scope to avoid full history analysis. Use when preparing a PR for review. Skip when the PR is a single trivial commit or description already exists.

LerianStudio/ring · 61 tokens

validate-changes

Evaluate staged changes using LLM-as-a-Judge before committing.

FlorianBruniaux/claude-code-ultimate-guide · 16 tokens

merge-contributor-pr

Take a contributor's pull request that cannot be merged as-is — usually a conflict with main — resolve the blocker without rewriting their commits, and merge it with a merge commit so their authorship survives. Detects the case where the conflict exists because the same feature already landed through another PR, and…

dyoshikawa/rulesync · 103 tokens

configuring-git-hygiene

Configure safe git workflow hygiene: pre-commit/pre-push hooks, Gitleaks secret scanning, .gitignore rules, local git config, and guardrails. Use when setting up git hooks, gitleaks/git leaks, staged pre-commit checks, pre-push validation, core.hooksPath, .gitignore, or git config best practices. NOT for creating…

alexei-led/cc-thingz · 111 tokens