tdd

Enforce Test-Driven Development with failing tests before production code.

38.5k|3.5k|Updated Jan 9, 2026

Search Tags:#unit tests #tdd #test-driven development #quality #red-green-refactor #software-engineering

Ready to run

npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode --skill tdd-yeachan-heo

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/Yeachan-Heo/oh-my-claudecode/tree/main/skills/tdd
Command: npx skills add https://github.com/Yeachan-Heo/oh-my-claudecode --skill tdd-yeachan-heo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams enforce Test-Driven Development by ensuring every feature starts with a failing test and follows a disciplined Red-Green-Refactor cycle, reducing defects and encouraging cleaner design.

Core Features & Use Cases

Red-Green-Refactor cadence: Guide to write a failing test first, implement minimal code to pass, then refactor for quality.
Enforcement Rules: Clear rules that stop production code before tests and ensure tests drive changes.
Use Case: When adding a new feature, provide a failing test, implement the minimal code, and verify all tests pass to confirm behavior.

Quick Start

Activate the TDD guidance for a feature by outlining the failing test first, then iterating through implement-and-test cycles until all tests pass.

Frequently Asked Questions about tdd

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce test-first development when adding new software features?▼

Test-first development is enforced by requiring a failing unit test before any production code is written, ensuring tests explicitly drive feature implementation and reduce software defects.

What is the Red-Green-Refactor cycle and how does it guide iterative development?▼

The Red-Green-Refactor cycle is a test-driven development process where you write a failing test, implement minimal code to pass it, then refactor for quality through continuous verification.

How do I start test-driven development for unit and integration workflows?▼

Start test-driven development by outlining a failing test for your unit or integration workflow, then iterate through implement-and-test cycles until all tests pass and behavior is verified.

Can I use test-driven development across different programming languages?▼

Yes, test-driven development can be applied across different programming languages, emphasizing test-first discipline, minimal implementations, and continuous verification for unit and integration workflows.

Why should I write a failing test before writing production code?▼

Writing a failing test before production code ensures that tests drive changes, encourages cleaner software design, and verifies that new behavior is explicitly defined before implementation.