From 4c7ef7d95b0f4fdb47dcce34e252dbdfbcd398a5 Mon Sep 17 00:00:00 2001 From: Trevin Chow Date: Mon, 13 Apr 2026 23:24:20 -0700 Subject: [PATCH] fix(ce-work): clarify combined-tree testing is safe for parallel batch Add note explaining that per-unit tests run on the combined working tree after parallel batch completion, which is acceptable because the Parallel Safety Check guarantees non-overlapping file sets. References issue #550 for full per-unit isolation via worktrees. Co-Authored-By: Claude Opus 4.6 (1M context) --- plugins/compound-engineering/skills/ce-work/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/plugins/compound-engineering/skills/ce-work/SKILL.md b/plugins/compound-engineering/skills/ce-work/SKILL.md index da461b9f..d96b5322 100644 --- a/plugins/compound-engineering/skills/ce-work/SKILL.md +++ b/plugins/compound-engineering/skills/ce-work/SKILL.md @@ -163,7 +163,7 @@ Determine how to proceed based on what was provided in ``. **After all parallel subagents in a batch complete:** 1. Wait for every subagent in the current parallel batch to finish before acting on any of their results - 2. For each completed unit, in dependency order: review the diff, run the relevant test suite, stage only that unit's files, and commit with a conventional message derived from the unit's Goal + 2. For each completed unit, in dependency order: review the diff, run the relevant test suite, stage only that unit's files, and commit with a conventional message derived from the unit's Goal. Note: tests run on the combined working tree containing all units' changes; this is acceptable because the Parallel Safety Check guarantees non-overlapping file sets, so no unit's tests are affected by another unit's edits. Full per-unit isolation via worktrees is tracked in issue #550. 3. If tests fail after merging a unit's changes, diagnose and fix before committing the next unit 4. Update the plan checkboxes and task list 5. Dispatch the next batch of independent units, or the next dependent unit