What is the core principle of this TDD skill?

The core principle is the Red-Green-Refactor cycle: write a test, watch it fail, write the minimal code to make it pass, and then clean up the code.

When should I use the TDD skill?

You should use it for all new features, bug fixes, and refactoring tasks. It is only skipped for throwaway prototypes or generated code.

Why does this skill insist on watching a test fail first?

Watching a test fail proves that the test is actually checking the intended behavior and isn't passing by accident or due to a configuration error.

What happens if I write code before a test?

Under the strict rules of this skill, any production code written before a failing test should be deleted and rewritten starting from the test to ensure proper design and verification.

Test-Driven Development (TDD)

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

bym16khb

安全与测试

Enforces a strict Red-Green-Refactor workflow to ensure production code is always verified by failing tests first.

关于

The Test-Driven Development (TDD) skill implements a disciplined approach to software engineering within Claude Code. By adhering to the 'Iron Law'—no production code without a failing test first—it ensures that every feature and bug fix is purposeful, documented by tests, and free from unnecessary complexity. This skill guides the AI and developer through the essential cycle of writing a failing test, implementing minimal code to pass, and refactoring for quality, ultimately reducing technical debt and preventing regressions.

主要功能

Mandatory failure verification to prevent false-positive tests
0 GitHub stars
Strict Red-Green-Refactor cycle enforcement
Minimalist code implementation to satisfy specific test requirements
Support for bug reproduction through failing integration tests
Comprehensive verification checklists for feature completion

使用场景

Refactoring complex logic while maintaining existing behavior through constant test feedback
Building robust new features with built-in documentation and verification
Fixing software bugs by reproducing them with tests to ensure permanent resolution

关于

主要功能

Mandatory failure verification to prevent false-positive tests
0 GitHub stars
Strict Red-Green-Refactor cycle enforcement
Minimalist code implementation to satisfy specific test requirements
Support for bug reproduction through failing integration tests
Comprehensive verification checklists for feature completion

使用场景

Refactoring complex logic while maintaining existing behavior through constant test feedback
Building robust new features with built-in documentation and verification
Fixing software bugs by reproducing them with tests to ensure permanent resolution