Review Delta

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

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

Steps

1. Ensure the graph is current by calling buildorupdategraphtool() (incremental update).

1. Get review context by calling getreviewcontext_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)

1. Analyze the blast radius by reviewing the impactednodes and impactedfiles 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)

1. 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 querygraphtool(pattern="testsfor", target=<functionname>) - Flag any untested changed functions

1. 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