review-changes
Perform a structured code review using change detection and impact
By tirth8205 · 194 installs
npx skills add tirth8205/code-review-graph --skill review-changes
Source repository · Upstream listing
Review Changes
Review a change set with risk scores and blast radius from the knowledge graph.
Steps
1. Call detect changes tool for risk scored changed functions, test gaps and affected flows.
2. Call get affected flows tool only when you need the steps of an affected flow.
3. For each high risk function, call query graph tool with pattern="tests for" to check test coverage.
4. Call get impact radius tool when the blast radius is not clear from step 1.
5. Suggest specific test cases for untested changes.
Output Format
Group findings by risk level (high, medium, low). For each finding give what changed and why it matters, its test coverage, and the suggested fix. End with a merge recommendation.
Token Efficiency Rules
Call get minimal context tool(task="<your task ") before any other graph tool.
Pass detail level="minimal" wherever a tool accepts it. Use "standard" only when minimal is not enough.
Prefer a targeted query graph tool call over a broad listing call.
Budget: about five tool calls and 800 tokens of graph output per task.
Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.