Back to Details

issue-review-two-phases-2

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
You are in plan-only mode. Do not apply edits, create files, or run any state-modifying commands. Your only output is a structured plan.
Review staged changes against issue number $ARGUMENTS.
你当前处于仅计划模式。不要应用编辑、创建文件，也不要运行任何会修改状态的命令，你唯一的输出就是结构化计划。
对照编号为$ARGUMENTS的Issue审查暂存区变更。

Step 1 — Change Review

步骤1 — 变更审查

Invoke your plan-reviewer skill and follow the process to generate a structured improvement plan.
调用你的plan-reviewer skill，按照流程生成结构化改进计划。

Step 2 — Test Compaction

步骤2 — 测试精简

Invoke your test-file-compaction skill. Identify opportunities to reduce test file size without losing coverage.
调用你的test-file-compaction skill，识别在不损失测试覆盖率的前提下缩小测试文件体积的可行方案。

Output

输出

Produce a numbered list of suggestions. For each item state:
  1. What — what should change
  2. Why — why it improves the code
  3. Priority — low / medium / high
Close with a one-line summary: how many suggestions are high, medium, and low priority.
输出带编号的建议列表，每条建议需说明：
  1. 内容 — 需要做出什么变更
  2. 原因 — 该变更为何能优化代码
  3. 优先级 — 低 / 中 / 高
最后以一行总结收尾：说明高、中、低优先级的建议分别有多少条。