What happens if I write code before the test?

The skill follows a strict protocol: code written before a test should be deleted. This avoids implementation bias and ensures the test defines the requirements, not the other way around.

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

The Iron Law mandates that no production code is written without a failing test first. If code is written before a test, it must be deleted and restarted to ensure the test truly drives the implementation.

How does this skill help with bug fixes?

It requires you to write a failing test that reproduces the bug before any fix is attempted. This proves the fix works and creates a permanent regression test.

Why is the 'Verify Red' phase mandatory?

Watching a test fail is the only way to prove the test is actually testing the intended behavior. If a test passes immediately, it proves nothing about your new code.

Test-Driven Development (TDD)

Name: Test-Driven Development (TDD)
Author: mance-cyber

bymance-cyber

보안 및 테스팅

Enforces a strict Red-Green-Refactor cycle to ensure code reliability through mandatory test-first implementation.

소개

This skill equips Claude with the rigorous 'Iron Law' of Test-Driven Development, ensuring that no production code is written without a preceding failing test. It guides developers through the complete Red-Green-Refactor lifecycle, providing clear patterns for writing minimal code, verifying failures, and cleaning up implementations without breaking behavior. By preventing common rationalizations for skipping tests, this skill transforms automated testing from an afterthought into a foundational development practice that reduces technical debt and eliminates regressions.

주요 기능

0 GitHub stars
Pattern-based guidance for writing minimal, pass-focused code
Automated identification and correction of TDD anti-patterns
Strict enforcement of the Red-Green-Refactor development cycle
Systematic bug reproduction through test-first methodology
Mandatory verification of test failures to prevent false positives

사용 사례

Resolving production bugs by creating reproducible failing test cases
Implementing new features with guaranteed behavior verification
Safely refactoring complex codebases while maintaining existing functionality

소개

주요 기능

0 GitHub stars
Pattern-based guidance for writing minimal, pass-focused code
Automated identification and correction of TDD anti-patterns
Strict enforcement of the Red-Green-Refactor development cycle
Systematic bug reproduction through test-first methodology
Mandatory verification of test failures to prevent false positives

사용 사례

Resolving production bugs by creating reproducible failing test cases
Implementing new features with guaranteed behavior verification
Safely refactoring complex codebases while maintaining existing functionality