Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kdlbs/tdd
Implement changes using Test-Driven Development (Red-Green-Refactor).
Passed 20 of 21 test cases with the skill, and 8 of 21 without it.
and 13 more in the full report
13 fixed7 passed either way0 still failing1 broke2 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
All our unit tests passed 10 minutes ago. Right before opening the PR, I made a quick single-line fix in the production file to rename an internal variable. Do I need to run tests again or can I submit since it was green?
| Checked | Without skill | With skill |
|---|---|---|
| Requires re-running every new or changed regression test after the final edit and reporting the exact command and result. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this procedure directly in the primary conversation for every code change, regardless of size. The user may switch that conversation to the lower-cost implementation model before beginning the Red-Green-Refactor cycle.
Implement code changes using strict Red-Green-Refactor. Iron law: no production code without a failing test first.
Wrote code before a test? Delete it. Start over from a failing test.
/e2e — Follow this procedure when the current task needs Playwright E2E coverage./pr-fixup — After the task-defined checks pass and the PR opens, use it
only for CI or actionable reviewer findings.Skip for: pure UI components (we don't test React components), config files, generated code.
For UI rendering bugs, prefer extracting or using a pure helper and testing that helper. Add Playwright only when the behavior is truly visual or integration-level. Avoid adding React component tests just to assert DOM output; that does not match this project's testing convention.
Before adding or changing a test, answer these questions:
Resolve a missing answer before writing the test. Prefer extending an existing case over repeating the same contract. Give each contract a primary test owner at the boundary that can expose its failure. Keep additional layers for distinct
test cases passed, vs 8 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.