review-delta

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Chinese

Perform a focused, token-efficient code review of only the changed code and its blast radius.

Token optimization: Before starting, call

get_docs_section_tool(section_name="review-delta")

for the optimized workflow. Use ONLY changed nodes + 2-hop neighbors in context.

对变更代码及其影响范围进行聚焦式、低Token消耗的代码审查。

Token优化： 开始前，请调用

get_docs_section_tool(section_name="review-delta")

获取优化工作流。上下文仅需包含变更节点 + 2跳邻接节点。

Ensure the graph is current by calling
```
build_or_update_graph_tool()
```
(incremental update).
Get review context by calling
```
get_review_context_tool()
```
. This returns:
- Changed files (auto-detected from git diff)
- Impacted nodes and files (blast radius)
- Source code snippets for changed areas
- Review guidance (test coverage gaps, wide impact warnings, inheritance concerns)
Analyze the blast radius by reviewing the
```
impacted_nodes
```
and
```
impacted_files
```
in the context. Focus on:
- Functions whose callers changed (may need signature/behavior verification)
- Classes with inheritance changes (Liskov substitution concerns)
- Files with many dependents (high-risk changes)
Perform the review using the context. For each changed file:
- Review the source snippet for correctness, style, and potential bugs
- Check if impacted callers/dependents need updates
- Verify test coverage using
```
query_graph_tool(pattern="tests_for", target=<function_name>)
```
- Flag any untested changed functions
Report findings in a structured format:
- Summary: One-line overview of the changes
- Risk level: Low / Medium / High (based on blast radius)
- Issues found: Bugs, style issues, missing tests
- Blast radius: List of impacted files/functions
- Recommendations: Actionable suggestions