Skip to content
Development
Skill

/review-delta

Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.

From plugin
code-review-graph
30k7 skills2 hooks1 MCP
Install
$ npx -y skills add tirth8205/code-review-graph --skill review-delta --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/review-delta

Context preview

The summary Claude sees to decide when to auto-load this skill.

Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.

SKILL.md

review-delta.SKILL.md
name: review-delta
description: Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
argument-hint: "[file or function name]"

Review Delta

Perform a focused, token-efficient code review of only the changed code and its blast radius.

**Token optimization:** Before starting, call `get_docs_section_tool(section_name="review-delta")` for the optimized workflow. Use ONLY changed nodes + 2-hop neighbors in context.

Steps

1. **Ensure the graph is current** by calling `build_or_update_graph_tool()` (incremental update).

2. **Get review context** by calling `get_review_context_tool()`. This returns:

  • Changed files (auto-detected from git diff)
  • Impacted nodes and files (blast radius)
  • Source code snippets for changed areas
  • Review guidance (test coverage gaps, wide impact warnings, inheritance concerns)

3. **Analyze the blast radius** by reviewing the `impacted_nodes` and `impacted_files` in the context. Focus on:

  • Functions whose callers changed (may need signature/behavior verification)
  • Classes with inheritance changes (Liskov substitution concerns)
  • Files with many dependents (high-risk changes)

4. **Perform the review** using the context. For each changed file:

  • Review the source snippet for correctness, style, and potential bugs
  • Check if impacted callers/dependents need updates
  • Verify test coverage using `query_graph_tool(pattern="tests_for", target=<function_name>)`
  • Flag any untested changed functions

5. **Report findings** in a structured format:

  • **Summary**: One-line overview of the changes
  • **Risk level**: Low / Medium / High (based on blast radius)
  • **Issues found**: Bugs, style issues, missing tests
  • **Blast radius**: List of impacted files/functions
  • **Recommendations**: Actionable suggestions

Advantages Over Full-Repo Review

  • Only sends changed + impacted code to the model (5-10x fewer tokens)
  • Automatically identifies blast radius without manual file searching
  • Provides structural context (who calls what, inheritance chains)
  • Flags untested functions automatically
Read more
Ships withcode-review-graph

Local-first code intelligence graph for MCP and CLI. Builds a persistent map of your codebase so AI coding tools read only what matters, with benchmarked context reductions on reviews and large-repo workflows.

Get the whole plugin
Stats
29,597
Stars
2,711
Forks
Active
Maintenance
Python
Language
MIT
License
7d ago
Last commit
5mo ago
Created

Repo: tirth8205/code-review-graph