What is the 'Iron Law' of this TDD skill?

The Iron Law dictates that no production code should be written without a failing test existing first. If code is written before a test, the skill advises deleting it and starting over to ensure the test truly validates the required behavior.

How does this skill handle bug fixes?

For bug fixes, the skill requires writing a test that reproduces the reported bug. Once the test fails as expected, you implement the minimal fix until the test turns green, ensuring the fix is verified and documented.

When should I skip TDD according to this skill?

Exceptions are rare but include throwaway prototypes, generated code, or simple configuration files. For all production features and behavior changes, the skill advocates for strict TDD adherence.

Why is it mandatory to watch a test fail?

Watching a test fail (the Red phase) proves that the test is actually checking the missing feature or bug. If a test passes immediately, it provides no evidence that it can catch a regression or that the new code is necessary.

Test-Driven Development (TDD) Workflow

Name: Test-Driven Development (TDD) Workflow
Author: lgbarn

bylgbarn

セキュリティとテスト

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

概要

The Test-Driven Development (TDD) skill mandates a high-integrity coding workflow centered around the 'Iron Law': no production code without a failing test first. By guiding Claude through the Red-Green-Refactor cycle, this skill ensures that every feature, bug fix, and refactor is backed by meaningful automated tests that verify behavior rather than just implementation. It provides rigorous checklists, identifies testing anti-patterns, and helps developers overcome common rationalizations for skipping tests, resulting in more maintainable, bug-resistant software.

主な機能

Comprehensive checklists for test quality and minimal code implementation
Strict enforcement of the Red-Green-Refactor cycle
Support for TDD-driven bug fixing and regression prevention
Mandatory verification of failing tests to prevent false positives
0 GitHub stars
Guidance on avoiding common testing anti-patterns and mocks misuse

ユースケース

Implementing new features with high-confidence regression protection
Fixing complex bugs by first reproducing the failure in a controlled test environment
Safely refactoring legacy codebases by establishing baseline behavioral tests

概要

主な機能

Comprehensive checklists for test quality and minimal code implementation
Strict enforcement of the Red-Green-Refactor cycle
Support for TDD-driven bug fixing and regression prevention
Mandatory verification of failing tests to prevent false positives
0 GitHub stars
Guidance on avoiding common testing anti-patterns and mocks misuse

ユースケース

Implementing new features with high-confidence regression protection
Fixing complex bugs by first reproducing the failure in a controlled test environment
Safely refactoring legacy codebases by establishing baseline behavioral tests