Are there any exceptions to using TDD with this skill?

TDD can be skipped for throwaway prototypes, generated code, or configuration files, but only after consulting with a human partner.

How does this skill handle the Red-Green-Refactor cycle?

It follows a strict loop: Write a failing test (Red), verify the failure, write the minimal code to pass (Green), verify the pass, and finally clean up the code (Refactor).

Why must I watch a test fail before writing code?

Watching a test fail proves that the test is actually checking the intended logic and ensures it isn't passing by accident or testing existing behavior.

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

The Iron Law dictates that no production code is written without a failing test first; if code is written before the test, it must be deleted and restarted.

Test-Driven Development (TDD)

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

bykgadek

セキュリティとテスト

Enforces a strict Red-Green-Refactor workflow to ensure high-quality, verified code implementation for every feature and bugfix.

概要

This skill integrates a rigorous Test-Driven Development (TDD) methodology into Claude's coding workflow, mandating that every feature or bug fix begins with a failing test. By adhering to the 'Iron Law' of no production code without a prior failing test, it eliminates technical debt, ensures clear design intent, and provides a systematic way to catch regressions before they reach production. It guides the AI through the complete Red-Green-Refactor cycle, emphasizing minimal implementation code and behavior-focused assertions.

主な機能

Strict enforcement of the Red-Green-Refactor cycle
Automatic identification and removal of non-TDD production code
Mandatory verification of test failures before implementation
Comprehensive verification checklists for bug fixes and new features
0 GitHub stars
Guidance on writing minimal, behavior-focused test cases

ユースケース

Safe refactoring of legacy systems with guaranteed regression protection
Fixing complex bugs by first reproducing them with a failing test
Developing new software features with 100% verified behavior

概要

主な機能

Strict enforcement of the Red-Green-Refactor cycle
Automatic identification and removal of non-TDD production code
Mandatory verification of test failures before implementation
Comprehensive verification checklists for bug fixes and new features
0 GitHub stars
Guidance on writing minimal, behavior-focused test cases

ユースケース

Safe refactoring of legacy systems with guaranteed regression protection
Fixing complex bugs by first reproducing them with a failing test
Developing new software features with 100% verified behavior