Test driven development
Skill kimtth/agent-skill-100-lines-or-less/skills/test-driven-development
🧿 Minimal but effective AI agent skill definitions in 100 lines or less.
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill test-driven-developmentAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when: implement a change with a TDD loop — failing test first, minimal fix, verify, refactor.
SKILL.md
1.0 KB, as published. Nobody here has run it
Goal: drive behavior with tests so code is correct by construction.
Use for:
- new behavior with a clear input/output contract
- bug fixes that need a regression guard
- code where you keep writing tests that only pass trivially
Workflow:
- Write one failing test that describes the desired behavior.
- Run it; confirm it fails for the right reason.
- Write the minimal code to make it pass.
- Run the suite; confirm green.
- Refactor with tests staying green.
- Repeat for the next behavior.
Test quality:
- assert observable behavior, not implementation detail
- one reason to fail per test
- cover edge cases and error paths, not just the happy path
Rules:
- never write production code without a failing test first
- do not test through mocks what you can test for real
- keep the red-green-refactor steps separate
- a test that cannot fail is not a test