Enforce red-green-refactor loops with behavior-focused integration tests.
npx skills add https://github.com/kyo0221/claude-config --skill tdd-kyo0221
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/kyo0221/claude-config/tree/main/skills/tdd Command: npx skills add https://github.com/kyo0221/claude-config --skill tdd-kyo0221
This skill solves the problem of writing fragile, implementation-coupled tests that break during code refactors, and helps developers build reliable, behavior-focused features using test-driven development.
Use the tdd skill to implement the new user password reset feature by first writing a test for successful password reset with a valid token, then building the minimal code to pass that test.
High-intent search queries and answers about installing and using this skill.
To write tests that survive code refactoring, use test-driven development to write integration-style tests that verify public interface behavior rather than internal implementation details. This behavior-focused approach prevents fragile, implementation-coupled tests.
The red-green-refactor loop in test-driven development is a workflow where you write a failing test first, implement the minimal code required to pass that test, and then safely refactor the code without breaking existing functionality.
Your tests break during changes because they are implementation-coupled rather than behavior-focused. Test-driven development should verify public interface behavior through integration tests, ensuring internal code changes and refactors do not cause test failures.
No, writing all tests first then all implementation is a horizontal slicing anti-pattern in test-driven development. This leads to low-quality, behavior-agnostic tests instead of reliable tests built through the red-green-refactor loop.
To add a new feature like a password reset using test-driven development, first write a test for the successful behavior with a valid token, then build the minimal code to pass that test, and finally refactor the implementation safely.
Yes, test-driven development applies to software engineering workflows for building new features, fixing bugs, and writing integration tests. It enforces practices that verify public interface behavior and eliminate implementation-coupled tests.
icyzhEnforce Test-Driven Development by creating failing tests before production code.
kartikkabadiGuides red-green-refactor workflows for behavior-first test-driven development.
LevezzeEnforce a red-green-refactor cycle for behavior-focused integration tests.
ReinaMacCredyEnforce the Red-Green-Refactor cycle by creating failing tests before production code.
