Apply the red-green-refactor loop to build integration-style tests.
npx skills add https://github.com/yashs33244/my-mac-claude --skill tdd-yashs33244
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/yashs33244/my-mac-claude/tree/main/skills/mattpocock/engineering/tdd Command: npx skills add https://github.com/yashs33244/my-mac-claude --skill tdd-yashs33244
This Skill helps you build or fix software by creating tests that verify behavior before you commit to an implementation, preventing regressions and unclear requirements.
Use the tdd skill when you need to implement or repair a feature or bug by asking for the next tracer-bullet test that targets a specific public behavior.
High-intent search queries and answers about installing and using this skill.
To apply test-driven development, you define behavior-first test cases, implement the minimum code required to pass each test sequentially, and refactor only after reaching a passing GREEN state. This red-green-refactor loop ensures reliable test coverage for new features.
The red-green-refactor loop in test-driven development is a process where you write a failing test, implement minimal code to make it pass, and then refactor the code. This cycle prevents regressions and ensures your implementation matches desired behaviors.
You fix bugs using behavior-first integration testing by creating tests that verify expected behavior through public interfaces before altering the implementation. This approach prevents unclear requirements and ensures your bug fix does not introduce regressions.
You should never refactor while tests are failing in the red-green-refactor loop. Refactoring guardrails require you to reach a passing GREEN state first, ensuring your structural changes do not alter the verified behavior.
Tracer bullets help with vertical slicing by targeting one specific public behavior at a time. This prevents horizontal slicing and guides you to iterate sequentially through desired behaviors, creating reliable integration-style tests.
The best way to prevent horizontal slicing is using tracer bullets within the test-driven development loop. This workflow forces you to iterate one behavior at a time, ensuring your integration tests exercise public interfaces rather than coupling to internal details.
whyte25Apply red-green-refactor with behavior-first integration-style tests.
brandtamDrive feature work with red-green-refactor loops and public interface tests.
mia-cxGuide developers through red-green-refactor loops for features and bug fixes.
AcendWayGuide test-driven development through the red-green-refactor loop.
