Does this skill support bug fixing?

Yes, it requires writing a failing test that reproduces the bug before implementing the fix, which proves the fix works and prevents future regressions of the same issue.

When should I use the TDD skill?

It should be used for all new features, bug fixes, refactorings, and behavior changes to ensure every modification is verified by an automated test suite.

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

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

What is the Red-Green-Refactor cycle?

It is a three-step process: write a failing test (Red), implement the minimal amount of code required to make the test pass (Green), and then clean up the code (Refactor) while ensuring the test remains green.

Why is writing tests after the code discouraged?

Tests written after code often suffer from implementation bias, passing immediately without proving they can actually catch bugs or accurately reflect requirements.

Test-Driven Development (TDD)

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

byabudhahir

•

Seguridad y Pruebas

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

Acerca de

The Test-Driven Development (TDD) skill transforms Claude into a disciplined coding partner that adheres to the 'Iron Law': no production code without a failing test first. It guides the development process through the mandatory Red-Green-Refactor cycle, ensuring every new feature or bug fix is verified against expected behavior before implementation. This skill is ideal for teams prioritizing code reliability and maintainability, as it prevents technical debt by treating untested code as invalid and requiring that developers witness a test failure before writing any functional logic.

Características Principales

Strict Red-Green-Refactor cycle enforcement
Bug reproduction through mandatory failing test cases
Guidance on writing minimal, passing implementation code to avoid over-engineering
Verification of test failure messages to ensure correct testing logic
Comprehensive TDD verification checklists for final code quality
1 GitHub stars

Casos de Uso

Reproducing and fixing bugs with automated regression protection
Safe refactoring of existing code while maintaining functional parity
Implementing new features with high reliability and documented behavior

Acerca de

Características Principales

Strict Red-Green-Refactor cycle enforcement
Bug reproduction through mandatory failing test cases
Guidance on writing minimal, passing implementation code to avoid over-engineering
Verification of test failure messages to ensure correct testing logic
Comprehensive TDD verification checklists for final code quality
1 GitHub stars

Casos de Uso

Reproducing and fixing bugs with automated regression protection
Safe refactoring of existing code while maintaining functional parity
Implementing new features with high reliability and documented behavior