Review Delta
Review only git-changed code with graph blast-radius context so solo builders ship diffs without re-reading the whole repo.
Overview
Review Delta is an agent skill most often used in Ship (also Build, Operate) that reviews only code changed since the last commit using graph-based blast-radius context.
Install
npx skills add https://github.com/tirth8205/code-review-graph --skill review-deltaWhat is this skill?
- Auto-detects changed files from git diff and limits context to changed nodes plus 2-hop graph neighbors
- Returns blast-radius guidance: callers, inheritance/Liskov concerns, wide-impact warnings, and test-coverage gaps
- Incremental graph refresh via build_or_update_graph_tool before get_review_context_tool
- Per-file review loop with query_graph_tool for tests_for coverage checks
- Optimized workflow doc via get_docs_section_tool(section_name="review-delta")
- 2-hop neighbor context limit for token optimization
Adoption & trust: 774 installs on skills.sh; 18.2k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You need a thorough review before merge but a full-repository pass burns tokens and misses which callers and tests actually matter.
Who is it for?
Solo builders with a code graph wired up who want commit-scoped reviews with automatic impact analysis.
Skip if: Greenfield projects without git history, repos without the graph tools installed, or teams that need formal compliance sign-off instead of agent-guided review.
When should I use this skill?
You want a focused review of changes since the last commit with automatic blast-radius detection from the code graph.
What do I get? / Deliverables
You get a structured delta review scoped to changed code, impacted dependents, and test gaps so you can fix regressions before merge or release.
- Per-changed-file review notes
- Blast-radius and test-coverage gap callouts
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Delta review is the canonical pre-merge gate in the Ship phase before you call a change safe to release. Fits the review subphase because it is explicitly a token-efficient code review workflow tied to commits and impacted callers.
Where it fits
After refactoring a shared service method, run delta review to see which API handlers and tests must be updated.
Before merging a PR, review only changed nodes and 2-hop neighbors instead of re-reading the monorepo.
On a production hotfix branch, verify inheritance and caller behavior for the minimal patch set.
How it compares
Use instead of pasting entire files into chat for review when you already maintain a dependency graph for the codebase.
Common Questions / FAQ
Who is review-delta for?
Solo and indie developers shipping from git who use code-review-graph tools and want cheaper, impact-aware reviews on every diff.
When should I use review-delta?
Use it in Ship before merging PRs, during Build when iterating on risky API changes, and in Operate when hotfixing production—any time you want changed-files-only review plus blast radius.
Is review-delta safe to install?
Treat it like any skill that drives git and graph tools: review the Security Audits panel on this Prism page and confirm what repositories and tools your agent can access before enabling it.
SKILL.md
READMESKILL.md - Review Delta
# 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