Review uncommitted changes using impact analysis. Quick local delta review with blast-radius detection.
How this skill is triggered — by the user, by Claude, or both
Slash command
/better-code-review-graph:review-deltaThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Perform a focused, token-efficient code review of uncommitted changes and their blast radius. Use this for quick local reviews BEFORE committing. For full branch/PR reviews, use review-pr instead.
Perform a focused, token-efficient code review of uncommitted changes and their blast radius. Use this for quick local reviews BEFORE committing. For full branch/PR reviews, use review-pr instead.
Token optimization: Before starting, call help(topic="graph") for the full actions reference. Use ONLY changed nodes + 2-hop neighbors in context.
Ensure the graph is current by calling graph(action="update").
Get review context by calling review(). This returns:
Analyze the blast radius by reviewing the impacted_nodes and impacted_files in the context. Focus on:
Perform the review using the context. For each changed file:
query(action="query", pattern="tests_for", target=<function_name>)Report findings in a structured format:
## Delta Review
### Summary
<One-line overview of the changes>
### Risk Level
- **Low**: Test-only changes, documentation, config files
- **Medium**: Implementation changes with <5 impacted files, no public API changes
- **High**: >5 impacted files OR public API signature/behavior change
### Issues Found
- <Bugs, style issues, missing tests>
### Blast Radius
- <List of impacted files/functions>
### Recommendations
1. <Actionable suggestion>
npx claudepluginhub n24q02m/claude-plugins --plugin better-code-review-graphReviews only code changes since last commit using graph-based impact analysis and blast radius detection. Provides token-efficient context for focused reviews of bugs, style, tests, and affected files/functions.
Assesses blast radius of code changes and reviews diffs by analyzing what touches what, what could break, which tests to run, and prior decisions. Use before refactors, renames, signature changes, or pull requests.
Reviews only changes since last commit using impact analysis and blast-radius detection for token-efficient delta code review.