Enforce a red-green-refactor test-driven development workflow with unit testing tooling.
npx skills add https://github.com/arinbalyan/config --skill tdd-arinbalyan
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/arinbalyan/config/tree/main/skills/tdd Command: npx skills add https://github.com/arinbalyan/config --skill tdd-arinbalyan
Test-driven development (TDD) guides teams to write failing tests before code, ensuring design clarity and early defect detection.
Use a test runner to define a failing test, then implement the feature to satisfy it.
High-intent search queries and answers about installing and using this skill.
Test-driven development (TDD) enforces a three-phase red-green-refactor cycle: write a failing test, implement minimal code to pass it, then refactor while keeping tests green. This ensures design clarity and early defect detection.
To implement a feature with test-driven development, start by writing tests that specify the desired behavior. Then, write the minimal code required to satisfy those tests, ensuring your API design and modularization are driven by the test specifications.
Test-driven development improves code quality by driving API design and modularization through tests, resulting in cleaner interfaces. Writing tests before code ensures early defect detection and provides confidence during refactoring.
Yes, you need a test runner to define failing tests when starting test-driven development. The workflow integrates with unit testing tooling to verify that your minimal feature implementation satisfies the specified behavior.
Refactoring in test-driven development occurs after your failing test passes with minimal code. You refactor your implementation while keeping the tests green, ensuring verifiable changes and incremental design improvements without breaking functionality.
DanomanicEnforce red-green-refactor cycles with failing tests before implementation.
CAPHTECHExecute prioritized refactoring steps with test-first verification in TypeScript projects.
jmstar85Enforce red-green-refactor cycles by writing failing tests before implementation.
AsiaOstrichGuide teams through ATDD workflows with Given-When-Then acceptance criteria.
