Review Changes
Review a change set with risk scores and blast radius from the knowledge graph.
Steps
- Call
detect_changes_toolfor risk-scored changed functions, test gaps and affected flows. - Call
get_affected_flows_toolonly when you need the steps of an affected flow. - For each high-risk function, call
query_graph_toolwithpattern="tests_for"to check test coverage. - Call
get_impact_radius_toolwhen the blast radius is not clear from step 1. - 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_toolcall 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.
