tdd-loop

Enforce a strict Red-Green-Refactor TDD loop with failing tests.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/LeeHusung/harness --skill tdd-loop-leehusung
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd-loop
Source: https://github.com/LeeHusung/harness/tree/main/.claude/skills/tdd-loop
Command: npx skills add https://github.com/LeeHusung/harness --skill tdd-loop-leehusung

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

엄격한 Red-Green-Refactor 사이클에서 구현체가 테스트에 의해 강제적으로 리팩토링되도록 돕고, 실패하는 테스트를 기반으로 한 의도를 안전하게 유지합니다.

Core Features & Use Cases

  • 엄격한 TDD 루프 수행: Red, Green, Refactor의 순서를 강제하고 테스트의 실패를 원인으로 삼아 구현을 개선합니다.
  • 최소 구현 원칙 준수: 실패한 테스트를 먼저 작성하고, 이를 만족시키기 위해 필요한 최소한의 코드를 구현합니다.
  • 커밋 및 리팩토링 가이드: 테스트 상태에 따라 커밋 메시지와 리팩토링 절차를 체계적으로 관리합니다.

Quick Start

테스트를 작성하고 실행하여 즉시 TDD 루프를 시작하세요.

Frequently Asked Questions about tdd-loop

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

FAQPage Schema
How do I enforce a strict Red-Green-Refactor TDD loop during daily development?

To enforce a strict Red-Green-Refactor TDD loop, you must first write a failing test, implement the minimal code required to pass it, and then execute disciplined refactoring steps with commit guardrails to ensure safe, incremental builds.

What is the minimal implementation principle in test-driven development?

The minimal implementation principle in test-driven development requires writing a failing test first and then producing only the absolutely necessary code to satisfy that test before proceeding to any structural refactoring.

When do I need a strict TDD cycle with commit guardrails for code reviews?

You need a strict TDD cycle with commit guardrails for code reviews when your team requires incremental, safe refactoring guided specifically by failing tests to ensure reliable builds and maintain code quality.

How do I manage refactoring procedures and commit messages based on unit test states?

You manage refactoring procedures and commit messages by enforcing the Red-Green-Refactor sequence, systematically tying commit messages and structural changes directly to the current passing or failing unit test states.

Does test-driven development work without writing failing unit tests before implementation?

No, strict test-driven development does not work without failing unit tests first, because the methodology specifically relies on applying a failing test to enforce and guide the minimal code implementation and subsequent safe refactoring.