Why does this skill insist on deleting code written without a test?

Writing code before the test violates the core TDD principle. Deleting and starting over ensures the test actually verifies the behavior and prevents the accumulation of unverified technical debt.

Can I use this skill for fixing existing bugs?

Yes. It requires writing a failing test that reproduces the bug before implementation, proving the fix works and preventing future regressions.

What if a test passes immediately during the RED phase?

If a test passes immediately, it means you are testing existing behavior or the test is flawed. The skill requires you to fix the test so it fails for the missing feature before proceeding.

Are mocks allowed in this TDD workflow?

Mocks are discouraged unless absolutely unavoidable. The skill prioritizes testing real behavior and API intent over testing the implementation details of mocks.

How does this skill handle refactoring?

It supports the 'Refactor' stage of the cycle, allowing you to clean up duplication and improve names only after a green test has established a verified safety net.

Test-Driven Development (TDD)

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

byeyadsibai

セキュリティとテスト

Enforces a strict Red-Green-Refactor cycle to ensure code quality and prevent technical debt through mandatory test-first development.

概要

This skill implements a rigorous Test-Driven Development (TDD) workflow for Claude, mandating that no production code is written without a preceding failing test. It guides developers through the foundational Red-Green-Refactor cycle, ensuring that every test is verified to fail before minimal code is written to pass it. By prohibiting 'test-after' patterns and requiring the deletion of unverified implementation code, it transforms Claude into a disciplined engineering partner that prioritizes long-term maintainability, behavioral integrity, and bug prevention.

主な機能

Mandatory test failure verification to ensure tests are valid and meaningful.
Strict enforcement of the 'Iron Law': No production code without a failing test first.
Standards for writing minimal, clear, and behavior-focused test suites without over-mocking.
Automated identification and rejection of common TDD rationalizations and shortcuts.
Guided Red-Green-Refactor workflow for features, bug fixes, and refactoring.
0 GitHub stars

ユースケース

Reproducing and fixing bugs by creating failing regression tests first.
Safely refactoring complex codebases by establishing a verified testing safety net.
Building new features with 100% confidence and comprehensive test coverage.

概要

主な機能

Mandatory test failure verification to ensure tests are valid and meaningful.
Strict enforcement of the 'Iron Law': No production code without a failing test first.
Standards for writing minimal, clear, and behavior-focused test suites without over-mocking.
Automated identification and rejection of common TDD rationalizations and shortcuts.
Guided Red-Green-Refactor workflow for features, bug fixes, and refactoring.
0 GitHub stars

ユースケース

Reproducing and fixing bugs by creating failing regression tests first.
Safely refactoring complex codebases by establishing a verified testing safety net.
Building new features with 100% confidence and comprehensive test coverage.