Guides test-driven development using red-green-refactor cycles with behavior-focused integration tests.
npx skills add https://github.com/zester4/zilmate --skill tdd-zester4
Please help me install this Agent Skill. Skill: tdd Source: https://github.com/zester4/zilmate/tree/main/.agents/skills/tdd Command: npx skills add https://github.com/zester4/zilmate --skill tdd-zester4
High-intent search queries and answers about installing and using this skill.
Write one failing test for a single behavior through the public interface, then write the minimal code to make it pass, and repeat per behavior. After all tests pass, refactor duplication and deepen modules while keeping tests green.
Good tests verify observable behavior through public APIs and survive internal refactors. Bad tests mock internal collaborators, test private methods, or assert on call counts, so they break when implementation changes without any behavior change.
Mock only at system boundaries such as external APIs, time, randomness, and sometimes databases or file systems. Never mock your own classes or internal collaborators, and design boundaries with dependency injection for easy mocking.
Writing all tests first produces tests of imagined behavior tied to data shapes and signatures rather than real behavior. Vertical slicing with one test then one implementation keeps each test grounded in what you just learned from the previous cycle.
Refactor only after all tests pass, never while a test is failing. Look for duplication, long methods, shallow modules, feature envy, and primitive obsession, running tests after each refactor step.
0xdeafcafeBackfill retroactive ADRs, Gherkin specs, and characterization tests for existing software features.
threadedstackDetects codebase changes and updates integration tests until the full suite passes.
Ramprasad4121Prepare codebases for security review with static analysis and documentation.
TheBushidoCollectiveGenerate Gherkin Given-When-Then BDD scenarios with acceptance criteria and edge cases.
