Review Changes

tirth8205/code-review-graph/skills/review-changes

作者 tirth82056b12d11625cbec3b6773e076cb3d136464fa90e5無授權條款收錄於 2026年10月9日更新於 2026年10月9日

Perform a structured code review using change detection and impact

AI 產生的概覽

使用知識圖譜工具對變更集進行結構化程式碼審查,評估風險並找出測試缺口。

功能
引導代理對變更集進行結構化程式碼審查。它呼叫知識圖譜工具來偵測帶風險評分的變更函式、測試缺口和受影響的流程,並檢查測試覆蓋率和影響範圍。結果依高、中、低風險分組,每項包含變更內容、重要性、測試覆蓋情況和建議修正方式,最後給出合併建議。
適用情境
適用於在合併前審查一組程式碼變更,並希望取得依風險排序的發現和覆蓋率缺口。適合能夠使用程式碼庫知識圖譜來縮小審查範圍的情境。
執行需求
需要存取所引用的知識圖譜工具(detect_changes_tool、get_affected_flows_tool、query_graph_tool、get_impact_radius_tool、get_minimal_context_tool)。僅為指示,不附帶指令碼。

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.

來源與署名

來源:tirth8205/code-review-graph位於skills/review-changes提交6b12d11

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架