OpenParable
Skip to content
← Back to skills

Review Delta

Testing & Quality
review-delta

Review Delta is an Agent Skill for testing & quality published in the tirth8205/code-review-graph repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

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

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/tirth8205/code-review-graph/blob/HEAD/skills/review-delta/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/review-delta, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

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