agentsclimarketplace
Sign in

Review delta

Skill demon24ru/code-review-graph/skills/review-delta

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

Install
npx -y skills add demon24ru/code-review-graph --skill review-delta

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, as published. Nobody here has run it

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)
    • Tip: call with summary_only=True first on large diffs to see scope (counts only, <1 KB), then without it for full details
    • Doc-only commits (.md, .txt, .yaml, .json, etc.) return code_changes: 0 immediately with no snippets — no wasted tokens

  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

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.