Can I skip TDD for small bug fixes or prototypes?

While exceptions can be made for throwaway prototypes with human permission, the skill advocates for TDD in all bug fixes and behavior changes to prevent regressions.

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

Watching a test fail proves that the test actually checks the intended behavior. If a test passes immediately, it may be testing the wrong thing or existing behavior, providing no proof of the new implementation's success.

What is the Iron Law of this TDD skill?

The Iron Law states that no production code should be written without a failing test existing first; if code is written before a test, it must be deleted and started over to ensure the test is valid.

How does the Red-Green-Refactor cycle work in this skill?

It follows a strict loop: Write a failing test (Red), verify it fails correctly, write the minimal code required to pass (Green), and finally clean up the code while keeping the tests passing (Refactor).

Test-Driven Development (TDD)

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

byorbtyapp

安全与测试

Enforces a strict Red-Green-Refactor workflow to ensure high-quality, verified code production through test-first implementation.

关于

The Test-Driven Development (TDD) skill transforms Claude into a disciplined engineering partner that adheres to the 'Iron Law' of software development: no production code without a failing test first. By guiding the LLM through the rigorous Red-Green-Refactor cycle, this skill ensures that every feature, bug fix, or refactoring effort is backed by automated tests, preventing regressions and reducing technical debt. It includes comprehensive logic for verifying failures, writing minimal code to pass, and performing safe refactoring while maintaining pristine test suites, making it an essential tool for developers who prioritize code reliability and long-term maintainability.

主要功能

Minimalist implementation logic to avoid over-engineering
Mandatory verification of failing tests to prevent false positives
Automated identification of TDD anti-patterns and shortcuts
Strict Red-Green-Refactor cycle enforcement
Integrated verification checklists for features and bug fixes
0 GitHub stars

使用场景

Refactoring complex legacy code safely with behavior-preserving tests
Reproducing and fixing bugs by creating failing test cases first
Building new features with comprehensive test coverage from the start

关于

主要功能

Minimalist implementation logic to avoid over-engineering
Mandatory verification of failing tests to prevent false positives
Automated identification of TDD anti-patterns and shortcuts
Strict Red-Green-Refactor cycle enforcement
Integrated verification checklists for features and bug fixes
0 GitHub stars

使用场景

Refactoring complex legacy code safely with behavior-preserving tests
Reproducing and fixing bugs by creating failing test cases first
Building new features with comprehensive test coverage from the start