Code-review-graph Review Changes

Name: Review Changes
Author: tirth8205

Perform a structured code review using change detection and impact

install

source · Clone the upstream repo

git clone https://github.com/tirth8205/code-review-graph

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/tirth8205/code-review-graph "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/review-changes" ~/.claude/skills/tirth8205-code-review-graph-review-changes && rm -rf "$T"

manifest: skills/review-changes/SKILL.md

source content

Review Changes

Perform a thorough, risk-aware code review using the knowledge graph.

Steps

Run
```
detect_changes
```
to get risk-scored change analysis.
Run
```
get_affected_flows
```
to find impacted execution paths.
For each high-risk function, run
```
query_graph
```
with pattern="tests_for" to check test coverage.
Run
```
get_impact_radius
```
to understand the blast radius.
For any untested changes, suggest specific test cases.

Output Format

Provide findings grouped by risk level (high/medium/low) with:

What changed and why it matters
Test coverage status
Suggested improvements
Overall merge recommendation

Token Efficiency Rules

ALWAYS start with
```
get_minimal_context(task="<your task>")
```
before any other graph tool.
Use
```
detail_level="minimal"
```
on all calls. Only escalate to "standard" when minimal is insufficient.
Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.