Guide test-driven development through red-green-refactor cycles with public interfaces.
npx skills add https://github.com/acaprino/claude-code-daodan --skill tdd-acaprino
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/acaprino/claude-code-daodan/tree/main/plugins/testing/skills/tdd Command: npx skills add https://github.com/acaprino/claude-code-daodan --skill tdd-acaprino
Tests verify behavior through public interfaces, enabling safer refactors and more reliable feature delivery by applying test-driven development principles.
Plan the feature by defining the public interface, write a single tracer bullet test that exercises it end-to-end, implement the minimal code to pass that test, and repeat until the feature is complete.
High-intent search queries and answers about installing and using this skill.
Begin test-driven development by defining the public interface, writing a single tracer bullet test for an end-to-end path, implementing minimal code to pass it, and repeating this incremental loop until the feature is complete.
The red-green-refactor cycle is a test-driven development workflow where you write a failing test, implement just enough code to pass it, and then refactor safely to improve structure without changing behavior.
Use a tracer bullet workflow in test-driven development to validate critical end-to-end paths early by writing a single test that exercises the public interface, ensuring safe incremental delivery before adding subsequent behaviors.
Test-driven development improves refactoring safety by verifying behavior through public interfaces. Passing tests confirm that structural changes during the refactor phase do not alter the expected user-facing behavior.
Yes, you should define public interfaces before writing integration tests in test-driven development. Aligning tests with user-facing behavior and predetermined interfaces ensures disciplined test-first workflows and safe incremental delivery.
The best way to enforce minimal implementation in test-driven development is to write failing tests first and implement only enough code to pass each test, repeating this incremental loop to avoid over-engineering and enable safe refactors.
Agentic-Engineering-AgencyGenerate unit and integration tests from SpecSafe specifications.
VYRE-StudiosRefactor code across languages while preserving behavior and validating tests.
pratikrath126Enforce a RED-GREEN-REFACTOR test-driven development workflow.
AcendWayGuide test-driven development through the red-green-refactor loop.
