Review Delta
- 972 installs
- 28.5k repo stars
- Updated August 2, 2026
- tirth8205/code-review-graph
review-delta is a code-review-graph skill that performs focused, token-efficient reviews on only changed code and its blast radius using dependency graph tools and 2-hop neighbor context.
About
review-delta is a skill from the code-review-graph project that reviews only changes since the last commit instead of entire repositories. It calls build_or_update_graph_tool for incremental graph updates, then get_review_context_tool to fetch changed nodes plus 2-hop neighbors for blast-radius analysis. Developers reach for it when they need thorough review feedback without blowing token budgets on unchanged files. The skill accepts an optional file or function name argument and loads an optimized workflow via get_docs_section_tool before starting.
- Reviews only git diff changes plus automatic blast-radius detection
- Uses graph-based impact analysis with 2-hop neighbors for context
- Calls build_or_update_graph_tool, get_review_context_tool and query_graph_tool automatically
- Focuses on callers, inheritance, dependents and test coverage gaps
- Token-optimized workflow that limits context to changed nodes
Review Delta by the numbers
- 972 all-time installs (skills.sh)
- +29 installs in the week ending Aug 4, 2026 (Skillselion tracking)
- Ranked #134 of 1,352 Code Review & Quality skills by installs in the Skillselion catalog
- Security screen: LOW risk (skills.sh audit)
- Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/tirth8205/code-review-graph --skill review-deltaAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 972 |
|---|---|
| repo stars | ★ 28.5k |
| Security audit | 3 / 3 scanners passed |
| Last updated | August 2, 2026 |
| Repository | tirth8205/code-review-graph ↗ |
How do you review only changed code efficiently?
Perform focused, token-efficient code reviews on only the changed portions of a codebase along with its blast radius.
Who is it for?
Developers using code-review-graph who want token-efficient reviews of recent commits with automatic impact analysis.
Skip if: Teams needing full-repository security audits or reviews without an incremental dependency graph built first.
When should I use this skill?
User requests a code review of recent changes, a delta review, or review with blast-radius analysis on a graph-enabled codebase.
What you get
A focused code review report covering changed nodes, 2-hop blast-radius dependencies, and findings limited to the delta.
- Delta code review report
- Blast-radius impact findings
By the numbers
- Limits review context to changed nodes plus 2-hop neighbors
Files
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
Related skills
Improve Codebase ArchitectureSafely deepen clusters of shallow modules into cohesive, testable units while respecting their external dependencies.566k196k
Caveman ReviewGet ultra-compressed, one-line code review comments that cut noise while keeping every actionable fix.270k94.7kCodebase DesignShared vocabulary for designing deep modules: improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable.266k196kCavecrewDelegate coding tasks to specialized subagents that return compressed output, keeping the main context window usable for much longer sessions.220k94.7kCode ReviewReviews a branch or PR diff on two axes at once: conformance to coding standards plus a code-smell baseline, and whether it actually implements the original spec.201k196k
Requesting Code ReviewDispatch a consistent, high-signal code reviewer subagent that catches plan deviations and quality issues before merging or continuing development.183k264kHow it compares
Choose review-delta over full-repo review skills when you have code-review-graph set up and need impact-aware feedback on recent commits only.
FAQ
How does review-delta reduce token usage?
review-delta limits context to changed nodes plus 2-hop neighbors from the code-review-graph instead of loading the full repository. It calls get_review_context_tool after an incremental build_or_update_graph_tool run.
What tools does review-delta require?
review-delta depends on code-review-graph tools: build_or_update_graph_tool, get_review_context_tool, and get_docs_section_tool for the optimized workflow. The graph must be current before review starts.
Is Review Delta safe to install?
skills.sh reports 3 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.