Why does this skill suggest deleting code written before a test?

Writing tests after code often results in tests that pass immediately without proving they actually catch errors. Deleting and restarting ensures the test truly verifies the intended behavior.

Does this skill help with code refactoring?

Absolutely. The 'Refactor' phase is the third step of the core cycle, allowing for code cleanup and optimization only after you have reached a 'Green' passing state.

How does TDD improve development speed in the long run?

While it requires more upfront effort, TDD reduces time spent on debugging, prevents regressions, and acts as living documentation, making the codebase easier to maintain.

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

The Iron Law states that no production code should be written without first having a failing test that demonstrates the need for that code. If code is written before a test, it should be deleted.

Can I use this skill for bug fixes?

Yes, it is highly recommended. The skill guides you to write a failing test that reproduces the bug, ensuring the fix is verified and preventing future regressions.

Test-Driven Development (TDD)

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

byLyQing63

0•

セキュリティとテスト

Enforces a strict Red-Green-Refactor workflow to ensure high-quality, bug-free production code.

This skill implements a rigorous Test-Driven Development (TDD) methodology within Claude Code, ensuring that no production code is written without a corresponding failing test first. It guides developers through the complete Red-Green-Refactor cycle, emphasizing minimal code implementation, verification of failure messages, and disciplined refactoring. By preventing common rationalizations for skipping tests, this skill helps create robust, self-documenting codebases with high confidence and minimal technical debt.

主な機能

01Mandatory verification of failure messages to ensure test validity

02Guided Red-Green-Refactor cycle instructions and visualizations

030 GitHub stars

04Detailed guidelines for writing minimal, purposeful implementation code

05Comprehensive verification checklist for TDD compliance and edge case coverage

06Strict enforcement of the 'Iron Law' (test before production code)

ユースケース

01Fixing software bugs by reproducing them with a failing test before applying a fix

02Safely refactoring existing logic while maintaining functional integrity through test suites

03Implementing new features with high reliability and clear architectural design

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add lyqing63/lyqing.opencode test-driven-development

For use in Claude.ai and ChatGPT

Download Skill