Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →michael-denyer/tdd
Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.
Passed 19 of 20 test cases with the skill, and 18 of 20 without it.
2 fixed17 passed either way0 still failing1 broke4 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am writing a bug fix report for `auth/jwt_validator.py` where expired tokens fail validation. In my report summary of the failing test, my teammate suggested I only quote the line `assert validate_token(token) == True`. Is quoting just that assertion line sufficient for demonstrating the failure?
| Checked | Without skill | With skill |
|---|---|---|
| States that quoting only the assertion line is insufficient. | Passed | Passed |
| Recommends quoting the failure mismatch output trimmed to the diff. | Missed | Passed |
The instructions your model reads when the skill loads.
When fixing a bug with a clear, cheap test path, make the broken behavior executable before changing production code. The goal is a focused regression test that fails before the fix and passes after it.
Do not force a test when it would be impractical. If the available test would require broad harness setup, brittle mocks, slow end-to-end infrastructure, production-only state, vague reproduction steps, or large unrelated fixture churn, skip adding a new test and use the closest useful verification instead.
Use the closest executable regression check instead: a targeted script, manual reproduction command, browser automation, snapshot comparison, log assertion, or focused integration check.
Prefer no new test over a bad test. A bad test is one that mostly tests mocks, encodes current implementation details, depends on timing or unrelated global state, needs expensive infrastructure for a small fix, or would be deleted immediately after proving the fix.
Report the evidence, not just the outcome:
test cases passed, vs 18 / 20 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.