Review Delta

tirth8205/code-review-graph/skills/review-delta

by tirth82056b12d11625cbec3b6773e076cb3d136464fa90e5No licenseListed Oct 9, 2026Updated Oct 9, 2026

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

Instructions onlySoftware Development
AI-generated overview

Reviews only code changed since the last commit, using impact analysis to find the blast radius and test gaps.

What it does
This skill guides an agent through a token-efficient delta code review. It calls graph and change-detection tools to obtain risk-scored changed functions, test gaps and affected flows, then optionally pulls minimal source snippets and review guidance. It produces a short report with a summary, a low/medium/high risk rating, issues, the blast radius of impacted files and functions, and recommendations.
When to use it
Use it when reviewing a recent code change and you want to focus only on what changed rather than the whole codebase. It suits pull-request-style reviews where impact on dependent code and missing tests matter.
Requirements
Requires the graph and change-detection tools named in the instructions (minimal context, graph build/update, change detection, review context, graph query) and access to git history via git diff against HEAD~1. Ships no scripts; instructions only.

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

Source and attribution

Source:tirth8205/code-review-graphinskills/review-deltaat commit6b12d11

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal