Why does the skill require me to watch a test fail?

Watching a test fail (the Red phase) is mandatory because it proves the test is actually checking the intended behavior and isn't passing due to a fluke or existing code.

What happens if I write the code before the test?

According to the skill's strict TDD principles, you should delete the code and start over. Writing tests after the fact often leads to biased tests that verify what you built rather than what was required.

Is this skill compatible with all programming languages?

Yes, the principles of Red-Green-Refactor are language-agnostic and can be applied to any environment where automated testing is possible.

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

The Iron Law states that no production code should be written without a failing test first. If code is written before a test, it must be deleted and rewritten following the TDD cycle.

Can I use this skill for bug fixes?

Absolutely. For bug fixes, the skill requires writing a test that reproduces the bug. Once the test fails, you write the minimal code to make it pass, ensuring the bug is truly fixed.

Test-Driven Development (TDD) Expert

Name: Test-Driven Development (TDD) Expert
Author: BbgnsurfTech

byBbgnsurfTech

•

セキュリティとテスト

Enforces a strict test-first development cycle to ensure code reliability and prevent technical debt.

概要

This skill implements an uncompromising framework for Test-Driven Development within Claude Code, guiding the AI through the essential Red-Green-Refactor lifecycle. It mandates that every line of production code is preceded by a failing test, ensuring that behavior is verified before implementation begins. By focusing on minimal code solutions and rigorous verification steps, it helps developers build maintainable, bug-free applications while eliminating the common pitfalls of writing tests as an afterthought. This skill acts as a disciplined engineering partner that prioritizes high-quality design and systematic verification over ad-hoc coding.

主な機能

Mandatory verification of test failures to prevent false positives
Integration with debugging workflows to ensure bugs are reproduced before fixing
Strict enforcement of the Red-Green-Refactor development cycle
Guidance on writing minimal, behavior-oriented tests over implementation tests
Identification and elimination of common TDD rationalizations and excuses
3 GitHub stars

ユースケース

Safely refactoring complex logic by maintaining a green test suite
Building new features with 100% verified test coverage from the start
Resolving bugs by creating failing regression tests before implementing fixes

概要

主な機能

Mandatory verification of test failures to prevent false positives
Integration with debugging workflows to ensure bugs are reproduced before fixing
Strict enforcement of the Red-Green-Refactor development cycle
Guidance on writing minimal, behavior-oriented tests over implementation tests
Identification and elimination of common TDD rationalizations and excuses
3 GitHub stars

ユースケース

Safely refactoring complex logic by maintaining a green test suite
Building new features with 100% verified test coverage from the start
Resolving bugs by creating failing regression tests before implementing fixes