tdd-workflow

Enforce red-green-refactor loops and prevent skipped tests in unit test workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces disciplined test-driven development by ensuring teams start from a failing test, make the minimal change to pass, and proceed to refactor only after green.

Core Features & Use Cases

  • Enforce red-green-refactor cycles: Start with a failing test, implement minimal changes to pass, and refactor safely after green.
  • Prevent skipped tests: Detect and prevent test.skip or describes.skip usage in the codebase.
  • Guidance for teams and CI: Works across local development and CI pipelines to maintain a predictable TDD workflow.

Quick Start

Begin each feature by failing a test, implement the minimal code to pass, then refactor only after green.

Frequently Asked Questions about tdd-workflow

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

FAQPage Schema
How do I enforce strict red-green-refactor loops in my development workflow?

You can enforce strict red-green-refactor loops by using rule-based guardrails that validate tests are run, changes are minimal, and refactoring occurs only after achieving a green test state.

What is the best way to prevent skipped tests like test.skip in a CI pipeline?

Preventing skipped tests in a CI pipeline requires applying automated guardrails that detect and block test.skip or describe.skip usage, ensuring all tests are executed.

How does TDD workflow guidance apply to both local development and CI pipelines?

TDD workflow guidance applies to both local development and CI pipelines by providing consistent rule-based validation that ensures developers start with failing tests before making minimal changes to pass.

Can I refactor my code before the test is green using TDD best practices?

No, TDD best practices mandate that refactoring occurs only after green, ensuring the test passes with minimal changes before you safely restructure the code.

Why should teams use TDD guardrails to validate minimal changes during unit testing?

Teams should use TDD guardrails to validate minimal changes because it enforces a predictable testing workflow, preventing skipped tests and ensuring disciplined test-driven development from failing-test starts to green outcomes.