Convert intended behavior into integration-style red-green-refactor cycles.
npx skills add https://github.com/ThorStarlord/interface-skills --skill tdd-thorstarlord
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/ThorStarlord/interface-skills/tree/main/skills/tdd Command: npx skills add https://github.com/ThorStarlord/interface-skills --skill tdd-thorstarlord
This Skill solves the problem of shipping buggy or fragile changes by turning intended behavior into integration-style tests that stay meaningful through refactors.
Use Case: You’re fixing a recurring bug and want confidence you didn’t break existing capabilities; write a single tracer bullet test for the user-visible behavior, implement minimally to pass it, then repeat for the next behavior until the fix is complete.
Use the tdd skill to rewrite your feature work as a sequence of one-test-at-a-time tracer bullets that verify user-facing behavior through public interfaces.
High-intent search queries and answers about installing and using this skill.
Test-driven development for bug fixes starts by writing a single failing test that exercises the public interface for the user-visible behavior, implementing minimally to pass it, and repeating until the fix is complete.
The red-green-refactor cycle means writing one failing test at a time, implementing the minimal code to pass it, then refactoring safely. It prevents horizontal slicing by avoiding large batches of tests written before understanding the actual behavior.
Integration tests survive refactoring by validating public interface behavior rather than internal implementation details. Behavior-focused tests avoid implementation-coupled assertions, ensuring tests stay meaningful through safe refactors.
Test-first development is less suitable when you cannot define clear public interface behavior or when rapid prototyping requires exploring implementations before locking down behavior-focused test expectations.
Mocking guidelines in test-driven development should focus on testing public interfaces and avoiding implementation-coupled assertions. Mocks should support behavior-focused testing without coupling to internal module structures that change during refactoring.
d3mingGuide developers through red-green-refactor test-driven development cycles.
Ni-BuEnforce test-driven development with a red-green-refactor workflow.
brujackGuide red-green-refactor cycles with integration-style tests through public interfaces.
saitarrunEnforce vertical tracer bullet red-green-refactor cycles for behavior-focused integration testing.
