Guide test-driven development with integration-style tests through public interfaces.
npx skills add https://github.com/IsKenKenYa/Commory --skill tdd-iskenkenya
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/IsKenKenYa/Commory/tree/main/.windsurf/skills/tdd Command: npx skills add https://github.com/IsKenKenYa/Commory --skill tdd-iskenkenya
It helps you avoid brittle, implementation-coupled tests by guiding you to write integration-style tests that specify observable behavior, then iterate through the red-green-refactor loop until the system works.
Use cases: Building new features, fixing bugs, and adding confidence to refactors in complex codebases where mocks and private-method assertions would create fragile coverage.
Use the tdd skill when you want to fix a bug or add a feature by writing one integration-style behavior test first, then implementing just enough to make it pass, repeating for the next behavior.
High-intent search queries and answers about installing and using this skill.
Use test-driven development to write integration-style tests that verify observable behavior through public interfaces. This approach avoids private-method assertions, ensuring tests specify what the system does rather than how it works internally.
The red-green-refactor loop involves writing one failing behavior test, implementing minimal code to pass it, then refactoring safely. This vertical slicing with tracer bullets prevents test code from outpacing real understanding of the feature.
Tests break during refactoring when they are coupled to implementation details via mocking or private-method assertions. Writing behavior-first integration tests through public interfaces keeps tests resilient to internal changes and prevents unnecessary test churn.
Set mocking boundaries at public interfaces to verify observable behavior rather than mocking internal calls. This prevents brittle, implementation-coupled assertions and ensures your bug fixing workflow maintains resistance to fragile test coverage.
Yes, test-driven development fits both feature building and bug fixing workflows. It guides you to write one integration-style behavior test first, implement just enough to pass, then repeat for the next behavior to add confidence in complex codebases.
Avoid horizontal slicing whenever test code outpaces real understanding of the system. Use vertical slicing with tracer bullets instead, writing one test at a time through red-green-refactor iteration to ensure tests reflect actual behavior.
JkkerGuide users through red-green-refactor cycles for test-driven development.
dhruvinrsoniDrive software implementation through the Red-Green-Refactor cycle.
sosensibleWrite and run BoxLang tests with mocking and data generation.
scute-shCreate executable BDD specifications using approval files with domain-specific language.
