review-delta — Claude Code skill: review changes
This skill reviews changes since the last commit and maps their blast radius. Use it for focused code review without loading the whole project.
npx skills add tirth8205/code-review-graph --skill review-delta -a claude-codeWhat review-delta does
review-delta reads changes from git diff against HEAD~1, scores changed functions for risk, and reports test gaps and affected flows. You can pass a file or function name to narrow the review scope.
The skill starts with get_minimal_context_tool. When the graph is not ready, it calls build_or_update_graph_tool, then uses detect_changes_tool and, when needed, get_review_context_tool. For each untested high-risk function, it checks related tests with query_graph_tool.
The report includes a one-line summary, risk level, issues, impacted files and functions, plus recommendations. Whole files are loaded only when a snippet cannot answer the question. A project graph must be available or built first, so its state affects the first review step.
What it helps with
- review only changes since the last commit
- find high-risk functions with a wide blast radius
- spot missing tests around changed code
- check which tests cover an untested function
- report impacted files, functions, and flows
Example prompts for the agent
- Run the `review-delta` skill on changes since the last commit.
- Use `review-delta` for `src/auth.ts` and show high-risk functions with their blast radius.
- Run `review-delta` and verify test coverage for every untested high-risk function.
How to install review-delta
1Skills CLI (Vercel)
npx skills add tirth8205/code-review-graph --skill review-delta -a claude-code2Manually: put the files in place
~/.claude/skills/review-delta/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/review-delta/
1Skills CLI (Vercel)
npx skills add tirth8205/code-review-graph --skill review-delta -a codex2Manually: put the files in place
.agents/skills/review-delta/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add tirth8205/code-review-graph --skill review-delta -a cursor2Manually: put the files in place
.cursor/skills/review-delta/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install tirth8205/code-review-graph review-delta2Manually: put the files in place
.github/skills/review-delta/SKILL.md1Skills CLI (Vercel)
npx skills add tirth8205/code-review-graph --skill review-delta -a gemini-cli2Platform CLI
gemini skills install https://github.com/tirth8205/code-review-graph --path skills/review-deltaManually: put the files in place
.devin/skills/review-delta/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add tirth8205/code-review-graph --skill review-delta -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set7
The whole set →Similar
Questions about review-delta
How do I install review-delta in Claude Code?
Run these steps in order: npx skills add tirth8205/code-review-graph --skill review-delta -a claude-code, then run npx skills add tirth8205/code-review-graph --skill review-delta -a claude-code again, and check ~/.claude/skills/review-delta/SKILL.md.
What does review-delta do?
It reviews changes against HEAD~1, scores their risk and blast radius, finds test gaps, and reports affected code and flows.
What happens when the project graph is not ready?
The skill calls build_or_update_graph_tool() and continues the change analysis. It uses query_graph_tool to confirm relationships such as tests for a function.
Source text
SKILL.md · MIT
--- name: review-delta description: Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection. argument-hint: "[file or function name]" --- # 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
© tirth8205 · MIT · tirth8205/code-review-graph