Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →mkurman/test-driven-development
Use when implementing any feature or bugfix, before writing implementation code
Passed 20 of 22 test cases with the skill, and 14 of 22 without it.
and 6 more in the full report
6 fixed14 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 6 test cases the skill fixed. Same model, same prompt, with and without the skill.
What test execution output criteria must be satisfied before marking a feature implementation complete?
| Checked | Without skill | With skill |
|---|---|---|
| Requires test run output to be completely pristine without errors or warnings | Missed | Passed |
| Requires all tests in the suite to pass | Missed | Passed |
The instructions your model reads when the skill loads.
---|------|-----|
| Minimal | One thing. "and" in name? Split it. | test('validates email and domain and whitespace') |
| Clear | Name describes behavior | test('test1') |
| Shows intent | Demonstrates desired API | Obscures what code should do |
"I'll write tests after to verify it works"
Tests written after code pass immediately. Passing immediately proves nothing:
Test-first forces you to see the test fail, proving it actually tests something.
"I already manually tested all the edge cases"
Manual testing is ad-hoc. You think you tested everything but:
Automated tests are systematic. They run the same way every time.
"Deleting X hours of work is wasteful"
Sunk cost fallacy. The time is already gone. Your choice now:
The "waste" is keeping code you can't trust. Working code without real tests is technical debt.
"TDD is dogmatic, being pragmatic means adapting"
TDD IS pragmatic:
test cases passed, vs 14 / 22 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.