Audit unit and integration tests for behavior-first vertical RED-GREEN cycles.
npx skills add https://github.com/tykhoncode/dicekit --skill tdd-quality
Please help me install this Agent Skill. Skill: tdd-quality Source: https://github.com/tykhoncode/dicekit/tree/main/.claude/skills/tdd-quality Command: npx skills add https://github.com/tykhoncode/dicekit --skill tdd-quality
tdd-quality reduces the risk of writing tests that don’t reflect real behavior by correcting two common TDD failure modes: horizontal slicing and tests coupled to implementation details.
Use cases include rebuilding a failing TDD flow, improving the quality of an existing test suite, and preventing refactor pain from tests that verify private implementation rather than user-visible behavior.
Apply the tdd-quality lens while doing TDD by choosing one high-value behavior, writing a tracer-bullet test that exercises the public interface, and iterating until the test proves behavior rather than internal structure.
High-intent search queries and answers about installing and using this skill.
To write unit tests that survive refactoring, validate behavior through public APIs rather than mocking internal seams. Apply a refactor resilience check by renaming internal symbols; if tests break without behavior changes, rewrite them to be behavior-first.
Horizontal slicing in TDD occurs when tests target implementation layers rather than complete behaviors. It reduces test quality by coupling assertions to internal structure, causing tests to fail during refactoring even when user-visible capabilities remain unchanged.
Stop testing implementation details by adopting behavior-first phrasing and vertical RED→GREEN cycles. Write tracer-bullet tests that exercise the public interface for one capability at a time, ensuring later tests are informed by actual system behavior rather than internal mocks.
Audit your test suite for refactor resilience when preparing for heavy codebase refactoring or rebuilding a failing TDD flow. Use the litmus check of renaming internal functions; fragile tests that break during this rename indicate dangerous coupling to private implementation.
Yes, behavior driven testing fixes a failing red green refactor cycle by enforcing vertical tracer-bullet slicing. You write one high-value behavior test against the public interface, iterate until it passes, and prevent horizontal slicing that causes future refactor pain.
Structure tests for user-visible capabilities by writing specifications that exercise public APIs rather than internal seams. Choose one high-value behavior, write a tracer-bullet test, and iterate vertically through the RED→GREEN cycle to ensure tests prove behavior instead of internal structure.
motoedieGuide test-driven development through red-green-refactor cycles for features and bug fixes.
mpsuesserDevelops software via a TDD cycle of Red-Green-Refactor with behavior-focused tests.
kaptinlinEnforce red-green-refactor TDD cycles for feature implementation.
Chang-Shih-YungAggregate type checker, linter, and test results into a 0-10 composite score.
