From a45ede8ddc0e0545a788868c83814b9d01fbf312 Mon Sep 17 00:00:00 2001 From: Jesse Vincent Date: Fri, 7 Aug 2026 18:44:56 -0700 Subject: [PATCH] feat(tdd): the project's suite defines green, not just your test file MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit At the Verify GREEN moment, redefine "other tests still pass": run the project's test command even when the task named only one test file — a scope statement bounds the deliverable, not the verification — and any failure seen goes in the report by name. In a pre-registered 24-rep battery on an adjacent-breakage probe, controls ran the wider suite in 1/12 sessions; with this text, 8/12 (sonnet 4/4, kimi 3/4, glm 1/4), and every session that saw the failure reported it. Claude-Session: https://claude.ai/code/session_0185AJr98gHx5EmwqNeft4Sy --- skills/test-driven-development/SKILL.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/skills/test-driven-development/SKILL.md b/skills/test-driven-development/SKILL.md index 4320d887..46838cc9 100644 --- a/skills/test-driven-development/SKILL.md +++ b/skills/test-driven-development/SKILL.md @@ -182,6 +182,16 @@ Confirm: **Other tests fail?** Fix now. +**"Other tests" means the project's suite, not just your file.** A +green run of the test you wrote is not a green suite. Before you call +the change done, run the project's test command (bare `pytest`, +`npm test`, `cargo test` — whatever the repo uses) even when your task +named only one test file. A scope statement in your task bounds the +deliverable, not your verification. Any failure that run shows — +including one you didn't cause — goes in your report by name; a red +test you watched scroll past and didn't mention is a report falsified +by omission. + ### REFACTOR - Clean Up After green only: