review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
Install
npx skills add https://github.com/tirth8205/code-review-graph --skill review-deltaSKILL.md
Review Delta
Review only the changed code and its blast radius.
Steps
- Call
get_minimal_context_tool(task="review changes"). If it returnsstatus: not_ready, callbuild_or_update_graph_tool()and continue. - Call
detect_changes_tool(detail_level="minimal")for risk-scored changed functions, test gaps and affected flows. Changes come fromgit diffagainstHEAD~1; if the argument names a file, pass it inchanged_files. - Call
get_review_context_tool(detail_level="minimal")when you need source snippets for the changed areas andreview_guidance(untested functions, wide blast radius, inheritance changes). - For each untested high-risk function, confirm with
query_graph_tool(pattern="tests_for", target="<function>"). - 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
Related skills
improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".
