Guide red-green-refactor TDD cycles for features and bug fixes.
npx skills add https://github.com/avoidthekitchen/avilingo-v2 --skill tdd-avoidthekitchen
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/avoidthekitchen/avilingo-v2/tree/main/.agents/skills/tdd Command: npx skills add https://github.com/avoidthekitchen/avilingo-v2 --skill tdd-avoidthekitchen
Test-driven development prevents regressions and ensures delivered behavior by driving implementation from failing tests through a disciplined red-green-refactor loop. It helps teams avoid fragile, implementation-coupled tests and focuses engineering effort on observable, user-facing behavior.
Guide the user through a single red-green-refactor cycle by asking which behavior to specify, writing one failing test for that behavior, implementing the minimal code to pass the test, and then running refactors.
High-intent search queries and answers about installing and using this skill.
Start test-driven development by writing one failing test for a specific behavior, implementing the minimal code to pass it, then refactoring safely. This iterative cycle ensures features are built incrementally and reliably while preventing regressions.
The best way to write integration tests is to exercise public interfaces and real code paths rather than mocking internal collaborators. This approach ensures tests verify observable behavior and remain resilient during structural refactors.
Avoid mocking internal collaborators during unit testing when specifying behaviors through public interfaces. Mocking internal components couples tests to implementation details, making them fragile and likely to break during valid refactoring cycles.
No, in TDD you must only refactor after reaching green. Running refactors only after tests pass ensures you preserve verified behavior while eliminating duplication, long methods, and deep module issues safely.
Yes, test-driven development works for fixing bugs in legacy code by incrementally adding integration tests for critical flows. Writing failing tests for bugs builds confidence and preserves observable behavior during subsequent improvements.
Dmccarty30Create isolated Git worktrees with dependency installation and baseline tests.
X-School-AcademyAutomate GitHub, CI/CD, Docker, and AWS infrastructure setup.
Jaydpatel01Enforce code correctness, readability, and safety with linters and type checkers.
NebulaMaoGenerate user stories, functional requirements, and acceptance criteria from natural language descriptions.
