How does this skill handle bug fixes?

It requires writing a failing test that reproduces the reported bug before any code is modified, ensuring the fix is verified and prevents future regressions.

Are there any exceptions to the TDD rule?

Exceptions include throwaway prototypes, generated code, and configuration files, though it is recommended to consult with a human partner before skipping the workflow.

What does 'Verify Red' mean in this context?

Verify Red is a mandatory step where the AI runs the newly written test to confirm it fails for the expected reason, proving the test is actually checking the missing functionality.

What is the primary rule of this TDD skill?

The 'Iron Law' is that no production code can be written without a failing test first; if code is written beforehand, it must be deleted and restarted to ensure the test truly validates the behavior.

Why is writing tests after the code discouraged?

Tests written after code are often biased by the implementation, proving only what the code does rather than what it should do, which can miss critical edge cases.

Test-Driven Development (TDD)

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

byEricGrill

•

セキュリティとテスト

Enforces a strict Red-Green-Refactor workflow to ensure high-quality, bug-free production code through test-first development.

概要

This Claude Code skill implements a rigorous Test-Driven Development (TDD) framework, requiring that a failing test be written and verified before any implementation code is allowed. It guides the AI through the complete TDD cycle—Red, Green, and Refactor—ensuring that every new feature or bug fix is backed by automated tests. By prohibiting production code that wasn't preceded by a failing test, this skill eliminates technical debt, prevents regressions, and promotes clean, minimalist software architecture that is easy to maintain.

主な機能

Mandatory verification of failing tests before implementation
2 GitHub stars
Minimalist code generation focused on passing specific tests
Anti-pattern detection and automated restart protocols
Strict Red-Green-Refactor cycle enforcement
Continuous refactoring guidance to maintain code health

ユースケース

Safely refactoring legacy codebases by establishing a test-driven safety net.
Resolving complex bugs by first reproducing them with a failing test case.
Developing new software features with 100% test coverage and high confidence.

概要

主な機能

Mandatory verification of failing tests before implementation
2 GitHub stars
Minimalist code generation focused on passing specific tests
Anti-pattern detection and automated restart protocols
Strict Red-Green-Refactor cycle enforcement
Continuous refactoring guidance to maintain code health

ユースケース

Safely refactoring legacy codebases by establishing a test-driven safety net.
Resolving complex bugs by first reproducing them with a failing test case.
Developing new software features with 100% test coverage and high confidence.