Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cursor/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 17 of 17 test cases with the skill, and 16 of 17 without it.
1 fixed16 passed either way0 still failing0 broke5 errored
Tokens, turns and time describe resource use, not a dollar price.
A test case the skill fixed. Same model, same prompt, with and without the skill.
A user reported: "The app sometimes freezes when rapidly tapping buttons on `CheckoutViewController.m`." We do not have clear steps or deterministic logs to reproduce it in an automated test. Should we create an automated UI test script from scratch before modifying any code?
| Checked | Without skill | With skill |
|---|---|---|
| The response advises against forcing an automated test when reproduction steps are vague. | Missed | Passed |
| The response recommends using targeted manual verification instead. | Passed | 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 16 / 17 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.