@wenaixi/dsh-superpower 7.4.1 → 7.5.2

package/skills/diagnosing-superpowers/templates/case.md

@@ -1,57 +1,64 @@
-# Case：<session-id>
+# Case: <session-id>
 
-workspace：~/.superpowers/diagnosing-superpowers/<session-id>/
-创建时间：<ISO 时间戳>
+Workspace: ~/.superpowers/diagnosing-superpowers/<session-id>/
+Created: <ISO timestamp>
 
-## 问题陈述（与你的 human partner 达成一致）
+## Problem statement (agreed with your human partner)
 
-<一段话。指明会话（们）、已知的回合范围、期望什么、发生了什么、以及重要的可观察量：墙钟时间、token 数、重复动作、某个具体的意外动作。>
+<One paragraph. Names the session(s), the turn range if known, what was
+expected, what happened, and the observable that matters: wall-clock,
+tokens, repeated actions, a specific unexpected action.>
 
-目标是提交 superpowers 缺陷报告：是 | 否
+Goal is a superpowers bug report: yes | no
 
-## 会话
+## Sessions
 
-| 角色 | 会话 id | 绝对路径 | 行数 | 字节 | 最长行（字节） | 首个 prompt（前 120 字符） | 首个时间戳 |
+| Role | Session id | Absolute path | Lines | Bytes | Longest line (bytes) | First prompt (first 120 chars) | First timestamp |
 |---|---|---|---|---|---|---|---|
-| 主会话 | | | | | | | |
+| main | | | | | | | |
 | subagent | | | | | | | |
 
-被拒候选：<id — 路径 — 拒绝原因>，或"无"。
+Rejected candidates: <id — path — why rejected>, or "none".
 
-读取时会话仍在运行：是 | 否（mtime <ISO>，行数 <N>）
+Session still running at read time: yes | no (mtime <ISO>, lines <N>)
 
-## 环境
+## Environment
 
-- OS：<名称与版本>
-- harness：<name> <version>
-- 所见模型：<model id — 位置（主会话 / subagent id）>
-- superpowers 安装根：<路径>；版本 <x.y.z>；git sha <sha 或 "not a checkout">
-- 会话期间读取或注入的技能文件：
+- OS: <name and version>
+- Harness: <name> <version>
+- Models seen: <model id — where (main / subagent id)>
+- Superpowers install root: <path>; version <x.y.z>; git sha <sha or "not a checkout">
+- Skill files read or injected during the session:
 
-| 技能 / 来源路径 | sha1 或不可用 | 来源 | 支撑位置 |
+| Skill / source path | sha1 or unavailable | Provenance | Supporting location |
 |---|---|---|---|
 
-把环境与技能观察标记为 历史证据 / 未验证快照 / 当前观察 / 未知。在宣布历史信息不可用之前，检查提供的来源说明、归档与被捕获的技能正文。缺失原始路径不会抹去保留的副本。当前版本/mtime 不能确立历史版本；一份被捕获的技能正文不能认证整个安装。
-
-- 已配置的其他插件 / 扩展 / MCP 服务器：<列表，或 "none found">
-- 存在的指令文件（仅路径）：<列表>
-
-## 这些文件的每个读者都应遵守的上下文安全规则
-
-- 读取此处列出的任何文件前，遵循 `references/context-safety.md`。
-- 在 subagent transcript 中，"user"是父代理。
-
-## 已发现来源与记录含义
-
-- 查阅的来源：<绝对路径、工具、帮助或文档来源>
-- 提取命令或查询：<对每个来源使用的有界命令或工具查询>
-- 目标身份证据：<会话 id、工作目录、时间戳、匹配内容与支撑记录位置>
-- 关联会话：<会话 id、关系与支撑记录位置，或 "none found">
-- 人类消息：<记录形状与含义证据>
-- 注入消息与父代理派发：<记录形状与含义证据>
-- 助手消息：<记录形状与含义证据>
-- 工具调用与结果：<记录形状、如何匹配及含义证据>
-- 用量计数器：<字段、增量或累计语义、单位与证据，或 "unavailable">
-- 时序：<字段、单位、事件边界与证据，或 "unavailable">
-- 其他相关记录：<模型、版本、压缩或其它含义与证据>
-- 未解决信息：<缺失、不可访问、歧义或不存在的信息，或 "none">
+Label environment and skill observations as historical evidence, unverified
+snapshot, current observation, or unknown. Check supplied provenance notes,
+archives and captured skill bodies before declaring historical information
+unavailable. Missing original paths do not erase retained copies. Current
+versions/mtimes do not establish historical versions; one captured skill body
+does not authenticate an entire installation.
+
+- Other plugins / extensions / MCP servers configured: <list, or "none found">
+- Instruction files present (paths only): <list>
+
+## Context-safety rules for every reader of these files
+
+- Follow `references/context-safety.md` before reading any file listed here.
+- In a subagent transcript, "user" is the parent agent.
+
+## Discovered sources and record meanings
+
+- Sources consulted: <absolute path, tool, help, or documentation source>
+- Extraction commands or queries: <bounded commands or tool queries used for each source>
+- Target identity evidence: <session id, working directory, timestamps, matching content, and supporting record locations>
+- Associated sessions: <session id, relationship, and supporting record locations, or "none found">
+- Human messages: <record shape and evidence for its meaning>
+- Injected messages and parent dispatches: <record shape and evidence for its meaning>
+- Assistant messages: <record shape and evidence for its meaning>
+- Tool calls and results: <record shapes, how they match, and evidence for those meanings>
+- Usage counters: <fields, incremental or cumulative semantics, units, and evidence, or "unavailable">
+- Timing: <fields, units, event boundaries, and evidence, or "unavailable">
+- Other relevant records: <models, versions, compactions, or other meanings and evidence>
+- Unresolved information: <missing, inaccessible, ambiguous, or absent information, or "none">

package/skills/diagnosing-superpowers/templates/issue.md

@@ -1,45 +1,51 @@
-标题：<技能或症状>：<一行可观察量>（<harness>）
+Title: <skill or symptom>: <one-line observable> (<harness>)
 
-- [x] 我已搜索现有 issue 且这不是重复（搜索：<查询词>；最接近：<#n 标题，或 "none">）
+- [x] I searched existing issues and this is not a duplicate (searched: <query terms>; closest: <#n title, or "none">)
 
-## 环境（必填）
+## Environment (required)
 
-| 字段 | 值 | 来源 / 支撑证据 |
+| Field | Value | Provenance / supporting evidence |
 |-------|-------|-------------------------------|
-| superpowers 版本 | <version>（<sha 或 "not a checkout">） | <历史证据 / 未验证快照 / 当前观察 / 未知>；<位置> |
-| harness (DSH) | <harness> | <标签>；<位置> |
-| harness 版本 | <version> | <标签>；<位置> |
-| 你的模型 + 版本 | <所见 model ids> | <标签>；<位置> |
-| 已安装的全部插件 | <列表> | <标签>；<位置> |
-| OS + shell | <os 版本>, <shell> | <标签>；<位置> |
+| Superpowers version | <version> (<sha or "not a checkout">) | <historical evidence / unverified snapshot / current observation / unknown>; <location> |
+| Harness (Claude Code, Cursor, etc.) | <harness> | <label>; <location> |
+| Harness version | <version> | <label>; <location> |
+| Your model + version | <model ids seen> | <label>; <location> |
+| All plugins installed | <list> | <label>; <location> |
+| OS + shell | <os version>, <shell> | <label>; <location> |
 
-## 这是 superpowers 问题还是平台问题？
+## Is this a Superpowers issue or a platform issue?
 
-- [ ] 我确认未安装 superpowers 时该问题不会出现
+- [ ] I confirmed this issue does not occur without Superpowers installed
 
-报告者尚未尝试在不安装 superpowers 的情况下复现。参与程度的证据见下；它不确立因果。
+The reporter has not tried reproducing without superpowers. Evidence for
+involvement is below; it does not establish cause.
 
-## 发生了什么？
+## What happened?
 
-<问题陈述，然后是分诊结论，`path:line` 引用改写为 `transcript line <n>`。>
+<Problem statement, then the triage verdict, with `path:line` citations
+rewritten as `transcript line <n>`.>
 
-## 复现步骤
+## Steps to reproduce
 
-1. <首个人类 prompt，已脱敏>
-2. <导致问题的回合，每行一个>
-3. <可观察量>
+1. <first human prompt, scrubbed>
+2. <the turns leading to the problem, one line each>
+3. <the observable>
 
-## 预期行为
+## Expected behavior
 
-<来自问题陈述>
+<from the problem statement>
 
-## 实际行为
+## Actual behavior
 
-<来自分诊结论>
+<from the triage verdict>
 
-## 调试日志或会话 transcript
+## Debug log or conversation transcript
 
-会话 id：<ids>。交付的本地归档：<路径，脱敏级别 <级别> | 未构建>。附加 bundle：<不声明；仅在批准后附加>。诊断报告所述的 superpowers 参与程度：<possible | likely>，证据位于 <transcript 行>。本报告不提出修复。
+Session id(s): <ids>. Delivered local archive: <path, redaction level <level>
+| none built>. Attached bundle: <no claim; attach only after approval>.
+Superpowers involvement per the diagnosis report: <possible | likely>, with
+evidence at <transcript lines>. This report does not propose a fix.
 
 ---
-使用 `diagnosing-superpowers` 技能提交。模型、harness、harness 版本与已安装插件列于上方。
+Filed with the `diagnosing-superpowers` skill. Model, harness, harness
+version, and installed plugins are listed above.

package/skills/diagnosing-superpowers/templates/report.md

@@ -1,76 +1,82 @@
-# 会话诊断：<session-id>
+# Session diagnosis: <session-id>
 
-报告路径：~/.superpowers/diagnosing-superpowers/<session-id>/report.md
-撰写时间：<ISO 时间戳>
+Report path: ~/.superpowers/diagnosing-superpowers/<session-id>/report.md
+Written: <ISO timestamp>
 
-## 1. 问题陈述（必填）
+## 1. Problem statement (REQUIRED)
 
-<从 case 文件复制。>
+<Copied from the case file.>
 
-## 2. 分诊结论（必填）
+## 2. Triage verdict (REQUIRED)
 
-<证据显示报告问题周围实际发生了什么。散文式，每条论断后带 `path:line`。说明置信度：高 / 中 / 低，以及什么能提高它。不陈述 superpowers 应该做什么。>
+<What the evidence shows happened around the reported problem. Prose, with
+`path:line` after every claim. State confidence: high / medium / low, and
+what would raise it. No statement about what superpowers should do.>
 
-## 3. 环境（必填）
+## 3. Environment (REQUIRED)
 
-- OS：
-- harness 与版本：
-- 所见模型：
-- superpowers 安装根 / 版本 / git sha：
-- 读取或注入的技能文件（来自 case 文件的 sha1 表）：
-- 其他插件、扩展、MCP 服务器：
-- 存在的指令文件（仅路径）：
+- OS:
+- Harness and version:
+- Models seen:
+- Superpowers install root / version / git sha:
+- Skill files read or injected (sha1 table from the case file):
+- Other plugins, extensions, MCP servers:
+- Instruction files present (paths only):
 
-把每个环境字段与技能观察标记为 历史证据 / 未验证快照 / 当前观察 / 未知，并记录其支撑证据位置。
+Label every environment field and skill observation as historical evidence,
+unverified snapshot, current observation, or unknown, and record its
+supporting evidence location.
 
-## 4. 检视的会话（必填）
+## 4. Sessions examined (REQUIRED)
 
-| 角色 | 会话 id | 绝对路径 | 行数 | 字节 |
+| Role | Session id | Absolute path | Lines | Bytes |
 |---|---|---|---|---|
 
-被拒候选：<id — 路径 — 原因>，或"无"。
+Rejected candidates: <id — path — why>, or "none".
 
-## 5. 时间线（必填）
+## 5. Timeline (REQUIRED)
 
-每条人类输入的 prompt 一行。事件列列出被调用的技能、派发的 subagent、压缩、错误、恢复、中止。
+One row per human-typed prompt. Events column lists skills invoked,
+subagents dispatched, compaction, errors, resumes, aborts.
 
-| 回合 | 行 | 时间 | 请求（一行） | 事件 |
+| Turn | Line | Time | Request (one line) | Events |
 |---|---|---|---|---|
 
-## 6. 发现（必填，每个维度一小节）
+## 6. Findings (REQUIRED, one subsection per dimension)
 
-每条发现：
+Each finding:
 ```
-- finding: <一句话>
-  evidence: <path:line> — "<短引文>"
-  turns: <首>–<末>
-  confidence: 高 | 中 | 低
+- finding: <one sentence>
+  evidence: <path:line> — "<short quote>"
+  turns: <first>–<last>
+  confidence: high | medium | low
 ```
-无内容可报的维度写 `none found — checked: <检查了什么>`。
+A dimension with nothing to report says `none found — checked: <what was checked>`.
 
-### 6.1 技能时间线
-### 6.2 计划遵守
-### 6.3 重复工作
-### 6.4 磕绊
-### 6.5 质量证据
-### 6.6 请求冲突
-### 6.7 成本与时间
-### 6.8 使用的其他插件与技能
+### 6.1 Skill timeline
+### 6.2 Plan adherence
+### 6.3 Repeated work
+### 6.4 Stumbles
+### 6.5 Quality evidence
+### 6.6 Request conflicts
+### 6.7 Cost and time
+### 6.8 Other plugins and skills used
 
-## 7. superpowers 参与程度（必填）
+## 7. Superpowers involvement (REQUIRED)
 
-未指示 | 可能 | 很可能
+not indicated | possible | likely
 
-证据行：<path:line 列表>。本节仅陈述参与程度。它不指认缺陷，也不提出修改。
+Evidence lines: <path:line list>. This section states involvement only. It
+does not name a defect and does not propose a change.
 
-## 8. 覆盖范围说明（必填）
+## 8. Coverage notes (REQUIRED)
 
-- 未读：<范围、文件与原因>
-- harness 功能不可用：<列表或无>
-- 读取时会话在进行中：是/否
-- 需要你的 human partner 复核：<列表或无>
+- Not read: <ranges, files, and why>
+- Harness features unavailable: <list or none>
+- Session was in progress at read time: yes/no
+- For your human partner to double-check: <list or none>
 
-## 9. 相似会话（仅应要求时）
+## 9. Similar sessions (only when requested)
 
-| 会话 id | 路径 | 日期 | harness | 匹配 | 未匹配 |
-|---|---|---|---|---|---|
+| Session id | Path | Date | Harness | Matched | Did not match |
+|---|---|---|---|---|---|

package/skills/dispatching-parallel-agents/SKILL.md

@@ -1,95 +1,97 @@
 ---
 name: dispatching-parallel-agents
-description: "Superpower Skill：面向 2 个以上无共享状态、无前后依赖的独立任务，并行委派多个 subagent 协同处理的高效分发模式。"
+description: "Superpower Skill: Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies"
+description_zh: "Superpower Skill：面向 2 个以上无共享状态、无前后依赖的独立任务，并行委派多个 subagent 协同处理的高效分发模式。"
 ---
 
-# 并行分发 agent
 
-## 概述
+# Dispatching Parallel Agents
 
-你将任务委派给拥有隔离上下文的专用 agent。通过精确构造指令与上下文，确保它们保持专注并成功完成任务。它们不应继承你当前会话的上下文或历史——你需要按需精确构造所需信息。这也能保留你自身的上下文，用于统筹协调工作。
+## Overview
 
-当存在多个互不相关的失败时（不同的测试文件、不同的子系统、不同的缺陷），串行排查会浪费大量时间。每一项排查都是独立的，可以并行进行。
+You delegate tasks to specialized agents with isolated context. By precisely crafting their instructions and context, you ensure they stay focused and succeed at their task. They should never inherit your session's context or history — you construct exactly what they need. This also preserves your own context for coordination work.
 
-**核心原则：** 每个独立的问题域分派一个 agent，让它们并发执行。
+When you have multiple unrelated failures (different test files, different subsystems, different bugs), investigating them sequentially wastes time. Each investigation is independent and can happen in parallel.
 
-## 何时使用
+**Core principle:** Dispatch one agent per independent problem domain. Let them work concurrently.
+
+## When to Use
 
 ```dot
 digraph when_to_use {
-    "存在多个失败？" [shape=diamond];
-    "是否相互独立？" [shape=diamond];
-    "由单个 agent 统一排查" [shape=box];
-    "每个问题域分配一个 agent" [shape=box];
-    "能否并行执行？" [shape=diamond];
-    "串行分发 agent" [shape=box];
-    "并行分发" [shape=box];
-
-    "存在多个失败？" -> "是否相互独立？" [label="是"];
-    "是否相互独立？" -> "由单个 agent 统一排查" [label="否 - 存在关联"];
-    "是否相互独立？" -> "能否并行执行？" [label="是"];
-    "能否并行执行？" -> "并行分发" [label="是"];
-    "能否并行执行？" -> "串行分发 agent" [label="否 - 存在共享状态"];
+    "Multiple failures?" [shape=diamond];
+    "Are they independent?" [shape=diamond];
+    "Single agent investigates all" [shape=box];
+    "One agent per problem domain" [shape=box];
+    "Can they work in parallel?" [shape=diamond];
+    "Sequential agents" [shape=box];
+    "Parallel dispatch" [shape=box];
+
+    "Multiple failures?" -> "Are they independent?" [label="yes"];
+    "Are they independent?" -> "Single agent investigates all" [label="no - related"];
+    "Are they independent?" -> "Can they work in parallel?" [label="yes"];
+    "Can they work in parallel?" -> "Parallel dispatch" [label="yes"];
+    "Can they work in parallel?" -> "Sequential agents" [label="no - shared state"];
 }
 ```
 
-**适用场景：**
-- 3 个以上测试文件失败，且根因各不相同
-- 多个子系统各自独立出现故障
-- 每个问题无需依赖其他问题的上下文即可理解
-- 各排查过程之间不存在共享状态
+**Use when:**
+- 3+ test files failing with different root causes
+- Multiple subsystems broken independently
+- Each problem can be understood without context from others
+- No shared state between investigations
 
-**不适用场景：**
-- 失败之间存在关联（修复一个可能顺带修复其他）
-- 需要理解完整的系统状态
-- agent 之间会相互干扰
+**Don't use when:**
+- Failures are related (fix one might fix others)
+- Need to understand full system state
+- Agents would interfere with each other
 
-## 使用模式
+## The Pattern
 
-### 1. 识别独立的问题域
+### 1. Identify Independent Domains
 
-按故障点对失败进行分组：
-- 文件 A 测试：工具审批流程
-- 文件 B 测试：批量完成行为
-- 文件 C 测试：中止功能
+Group failures by what's broken:
+- File A tests: Tool approval flow
+- File B tests: Batch completion behavior
+- File C tests: Abort functionality
 
-每个领域都是独立的——修复工具审批不会影响中止相关的测试。
+Each domain is independent - fixing tool approval doesn't affect abort tests.
 
-### 2. 创建聚焦的 agent 任务
+### 2. Create Focused Agent Tasks
 
-每个 agent 应获得：
-- **明确范围：** 单个测试文件或子系统
-- **清晰目标：** 让这些测试通过
-- **约束条件：** 不得改动其他代码
-- **预期输出：** 发现了什么、修复了什么的总结
+Each agent gets:
+- **Specific scope:** One test file or subsystem
+- **Clear goal:** Make these tests pass
+- **Constraints:** Don't change other code
+- **Expected output:** Summary of what you found and fixed
 
-### 3. 并行分发
+### 3. Dispatch in Parallel
 
-在同一条回复中一次性发起全部三个 subagent 分发——它们将并行运行：
+Issue all three subagent dispatches in the same response — they run in parallel:
 
 ```text
 Subagent (general-purpose): "Fix agent-tool-abort.test.ts failures"
 Subagent (general-purpose): "Fix batch-completion-behavior.test.ts failures"
 Subagent (general-purpose): "Fix tool-approval-race-conditions.test.ts failures"
-# 全部三个并发执行。
+# All three run concurrently.
 ```
 
-在同一条回复中发起多次分发调用 = 并行执行。每条回复只发一次 = 串行执行。
+Multiple dispatch calls in one response = parallel execution. One per response = sequential.
 
-### 4. 复核与集成
+### 4. Review and Integrate
 
-当 agent 返回后：
-- 阅读每一份总结
-- 验证各修复之间是否存在冲突
-- 运行完整测试套件
-- 整合所有变更
+When agents return:
+- Read each summary
+- Verify fixes don't conflict
+- Run full test suite
+- Integrate all changes
 
-## agent prompt 结构
+## Agent Prompt Structure
 
-优秀的 agent prompt应具备：
-1. **聚焦** - 一个清晰的问题域
-2. **自包含** - 包含理解问题所需的全部上下文
-3. **输出明确** - agent 应该返回什么？
+Good agent prompts are:
+1. **Focused** - One clear problem domain
+2. **Self-contained** - All context needed to understand the problem
+3. **Specific about output** - What should the agent return?
 
 ```markdown
 Fix the 3 failing tests in src/agents/agent-tool-abort.test.ts:
@@ -112,56 +114,56 @@ Do NOT just increase timeouts - find the real issue.
 Return: Summary of what you found and what you fixed.
 ```
 
-## 常见错误
+## Common Mistakes
 
-**[FAIL] 范围过大：** "修复所有测试" - agent 容易迷失方向
-**[OK] 具体明确：** "修复 agent-tool-abort.test.ts" - 范围聚焦
+**[FAIL] Too broad:** "Fix all the tests" - agent gets lost
+**[OK] Specific:** "Fix agent-tool-abort.test.ts" - focused scope
 
-**[FAIL] 缺乏上下文：** "修复竞态条件" - agent 不知道位置
-**[OK] 提供上下文：** 粘贴错误信息和测试名称
+**[FAIL] No context:** "Fix the race condition" - agent doesn't know where
+**[OK] Context:** Paste the error messages and test names
 
-**[FAIL] 缺少约束：** agent 可能会重构所有内容
-**[OK] 明确约束：** "不要改动生产代码" 或 "仅修复测试"
+**[FAIL] No constraints:** Agent might refactor everything
+**[OK] Constraints:** "Do NOT change production code" or "Fix tests only"
 
-**[FAIL] 输出模糊：** "修好它" - 你无法知道改了什么
-**[OK] 输出具体：** "返回根因与变更总结"
+**[FAIL] Vague output:** "Fix it" - you don't know what changed
+**[OK] Specific:** "Return summary of root cause and changes"
 
-## 何时不应使用
+## When NOT to Use
 
-**存在关联的失败：** 修复一个可能顺带修复其他——应先一起排查
-**需要完整上下文：** 理解问题需要看到整个系统
-**探索式调试：** 尚不清楚哪里出了问题
-**存在共享状态：** agent 会相互干扰（编辑同一文件、占用同一资源）
+**Related failures:** Fixing one might fix others - investigate together first
+**Need full context:** Understanding requires seeing entire system
+**Exploratory debugging:** You don't know what's broken yet
+**Shared state:** Agents would interfere (editing same files, using same resources)
 
-## 来自真实会话的示例
+## Real Example from Session
 
-**场景：** 大规模重构后，3 个文件共出现 6 个测试失败
+**Scenario:** 6 test failures across 3 files after major refactoring
 
-**失败情况：**
-- agent-tool-abort.test.ts：3 个失败（时序问题）
-- batch-completion-behavior.test.ts：2 个失败（工具未执行）
-- tool-approval-race-conditions.test.ts：1 个失败（执行次数为 0）
+**Failures:**
+- agent-tool-abort.test.ts: 3 failures (timing issues)
+- batch-completion-behavior.test.ts: 2 failures (tools not executing)
+- tool-approval-race-conditions.test.ts: 1 failure (execution count = 0)
 
-**决策：** 属于独立领域——中止逻辑、批量完成、竞态条件三者相互分离
+**Decision:** Independent domains - abort logic separate from batch completion separate from race conditions
 
-**分发：**
+**Dispatch:**
 ```
 Agent 1 → Fix agent-tool-abort.test.ts
 Agent 2 → Fix batch-completion-behavior.test.ts
 Agent 3 → Fix tool-approval-race-conditions.test.ts
 ```
 
-**结果：**
-- Agent 1：用基于事件的等待替代了固定超时
-- Agent 2：修复了事件结构缺陷（threadId 位置错误）
-- Agent 3：增加了对异步工具执行完成的等待
+**Results:**
+- Agent 1: Replaced timeouts with event-based waiting
+- Agent 2: Fixed event structure bug (threadId in wrong place)
+- Agent 3: Added wait for async tool execution to complete
 
-**集成：** 所有修复相互独立，无冲突，全量测试通过
+**Integration:** All fixes independent, no conflicts, full suite green
 
-## 验证
+## Verification
 
-agent 返回后：
-1. **复核每份总结** - 理解变更内容
-2. **检查是否存在冲突** - agent 是否编辑了同一段代码？
-3. **运行全量测试** - 验证所有修复协同工作正常
-4. **抽样检查** - agent 可能存在系统性错误
+After agents return:
+1. **Review each summary** - Understand what changed
+2. **Check for conflicts** - Did agents edit same code?
+3. **Run full suite** - Verify all fixes work together
+4. **Spot check** - Agents can make systematic errors