When should I use the TDD skill?

You should use it for all new features, bug fixes, refactoring, and behavior changes. Exceptions are only made for throwaway prototypes, generated code, or configuration files.

Can I keep code I wrote before the test as a reference?

No. The skill strictly requires deleting any production code written before a test to ensure the test is truly validating the behavior and not biased by existing implementation.

How does this skill help with bug fixes?

It requires writing a failing test that reproduces the bug before any fix is applied, ensuring the fix is verified, prevents regressions, and serves as documentation for the fix.

What is the Iron Law in this TDD skill?

The Iron Law mandates that no production code should be written without first having a failing test that demonstrates the need for that code. If code is written before the test, it must be deleted and rewritten.

Test-Driven Development (TDD)

Name: Test-Driven Development (TDD)
Author: ehartye

byehartye

0•

보안 및 테스팅

Enforces a strict Red-Green-Refactor workflow to ensure all production code is validated by failing tests before implementation.

The Test-Driven Development (TDD) skill implements a rigorous methodology within Claude Code, mandating that every feature or bug fix begins with a failing test. By adhering to the 'Iron Law'—no production code without a prior failing test—it eliminates technical debt, prevents regressions, and ensures that automated tests accurately validate system behavior rather than just implementation details. It provides clear guidance on the TDD cycle, helps identify common rationalizations for skipping tests, and integrates seamlessly with complex development workflows to ensure high-quality, maintainable software.

주요 기능

01Enforces the 'Iron Law' of no production code without a failing test

02Guides users through the complete Red-Green-Refactor lifecycle

030 GitHub stars

04Provides standardized verification checklists for test failures and passes

05Facilitates bug reproduction through mandatory failing integration tests

06Identifies and prevents common TDD rationalizations and anti-patterns

사용 사례

01Safely refactoring existing codebases by maintaining functional parity through continuous verification

02Fixing bugs by first creating a reproducible failing test case to prevent regressions

03Building new features with high confidence and minimal technical debt

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add ehartye/hartye-superpowers test-driven-development

For use in Claude.ai and ChatGPT

Download Skill