What happens if I write code before the test?

According to the skill's 'Iron Law,' if you write production code before a test, you must delete that code and start over to ensure the implementation is truly driven by the requirements.

Does this skill work for bug fixes?

Yes. When a bug is found, the skill requires writing a test that reproduces the bug (Red), watching it fail, and then writing the minimal code to fix it (Green).

What is the core principle of this TDD skill?

The core principle is to write a failing test before any production code. If you didn't watch the test fail, you don't have proof that the test is verifying the correct behavior.

When should I skip TDD using this skill?

Exceptions are rare and should be discussed with a human partner; they typically only include throwaway prototypes, generated code, or basic configuration files.

Test-Driven Development (TDD)

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

byjasir

보안 및 테스팅

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

소개

This skill implements a strict Test-Driven Development (TDD) protocol for Claude Code, mandating the 'Iron Law' that no production code be written without a preceding failing test. It guides developers through the complete lifecycle of writing a minimal test, verifying the failure, implementing the simplest possible solution, and refactoring for clean design. By systematically preventing technical debt and ensuring every behavior is documented through automation, this skill transforms Claude into a disciplined development partner that prioritizes code reliability and long-term maintainability.

주요 기능

Strict Red-Green-Refactor cycle enforcement
0 GitHub stars
Mandatory verification of failing tests to prevent false positives
Guidance on writing minimal, behavior-oriented implementation code
Integrated verification checklists for feature completion and bug fixes
Detection and mitigation of common TDD rationalizations and anti-patterns

사용 사례

Fixing bugs by first creating reproducible failing test cases
Safely refactoring complex logic while maintaining verified green states
Building robust new features with built-in regression protection

소개

주요 기능

Strict Red-Green-Refactor cycle enforcement
0 GitHub stars
Mandatory verification of failing tests to prevent false positives
Guidance on writing minimal, behavior-oriented implementation code
Integrated verification checklists for feature completion and bug fixes
Detection and mitigation of common TDD rationalizations and anti-patterns

사용 사례

Fixing bugs by first creating reproducible failing test cases
Safely refactoring complex logic while maintaining verified green states
Building robust new features with built-in regression protection