claudegoodies
Skill

Review Changes

From tirth8205

Perform a structured code review using change detection and impact

Runs a fixed sequence of graph tools to review changes by risk, test coverage, and impact radius.

Use it when

  • Reviewing a PR and want risk-scored change analysis before merging
  • Need to check test coverage for functions touched by a diff
  • Want blast-radius/impact analysis of a code change

Skip it if

  • You don't have the underlying knowledge-graph tools (detect_changes_tool, query_graph_tool, etc.) set up
  • You want a simple diff review, not a multi-step graph-based workflow
  • No test suite exists to check 'tests_for' coverage against

Facts

Repository
tirth8205/code-review-graph
Status
Actively maintained
Last commit
Source file
skills/review-changes/SKILL.md

Source preview

The instructions Claude Code reads when this skill runs.

## Review Changes

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

### Steps

1. Run `detect_changes_tool` to get risk-scored change analysis.
2. Run `get_affected_flows_tool` to find impacted execution paths.
3. For each high-risk function, run `query_graph_tool` with pattern="tests_for" to check test coverage.
4. Run `get_impact_radius_tool` to understand the blast radius.
5. 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.
View full source on GitHub →

Other skills