Why is watching a test fail (RED) mandatory?

Watching a test fail proves that the test is actually checking the intended behavior. If a test passes immediately, it provides no evidence that your new code is working or necessary.

How does this skill handle refactoring?

Refactoring is only permitted during the 'Green' phase. Once a test passes, you can clean up the code while running tests frequently to ensure the behavior remains correct.

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

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

Can I use this skill for bug fixes?

Yes. The skill requires you to write a failing test that reproduces the bug before writing any code to fix it, ensuring the bug is truly resolved and won't return.

Test-Driven Development (TDD)

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

byKrosebrook

•

Seguridad y Pruebas

Enforces a strict Red-Green-Refactor workflow to ensure all production code is verified by failing tests before implementation.

Acerca de

This skill transforms Claude into a disciplined TDD practitioner by mandating the 'Iron Law': no production code is written without a failing test first. It guides the AI through the rigorous Red-Green-Refactor cycle, ensuring that tests actually verify behavior by requiring a confirmed failure before any implementation. By following this systematic approach, the skill helps developers eliminate technical debt, prevent regressions, and create self-documenting codebases where every feature is backed by a purposeful test suite.

Características Principales

Strict enforcement of the Red-Green-Refactor development cycle
Mandatory verification of test failure messages to avoid false positives
Automated verification checklists for completing features and bug fixes
Guidelines for avoiding common TDD rationalizations and shortcuts
1 GitHub stars
Minimalist code implementation strategies to pass tests efficiently

Casos de Uso

Reproducing and fixing bugs by creating regression tests first
Refactoring complex logic while maintaining existing behavioral guarantees
Building mission-critical features where reliability is the top priority

Acerca de

Características Principales

Strict enforcement of the Red-Green-Refactor development cycle
Mandatory verification of test failure messages to avoid false positives
Automated verification checklists for completing features and bug fixes
Guidelines for avoiding common TDD rationalizations and shortcuts
1 GitHub stars
Minimalist code implementation strategies to pass tests efficiently

Casos de Uso

Reproducing and fixing bugs by creating regression tests first
Refactoring complex logic while maintaining existing behavioral guarantees
Building mission-critical features where reliability is the top priority