tdd

Enforce a TDD workflow from failing tests to passing implementations with conventional commits.

14|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/tae0y/python-project-template --skill tdd-tae0y
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tdd
Source: https://github.com/tae0y/python-project-template/tree/main/.claude/skills/tdd
Command: npx skills add https://github.com/tae0y/python-project-template --skill tdd-tae0y

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TDD is the backbone of safe, maintainable code. This workflow enforces a consistent Test-Driven Development process across all production changes, guiding teams from failing tests to passing implementations.

Core Features & Use Cases

  • Red-Green-Refactor cycle to ensure incremental delivery.
  • TDD evidence and disciplined commit history for easier reviews.
  • Workflow integration with PRs, tests, and linting to maintain code quality.

Quick Start

Create a failing test for a small feature, then implement only the minimum code to pass, and commit the change.

Frequently Asked Questions about tdd

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

FAQPage Schema
How do I enforce a consistent TDD workflow across all code changes?

To enforce a consistent TDD workflow, this process guides developers from clearly failing tests to passing implementations, requiring a standard testing framework and conventional commit messages to maintain the RED-GREEN-REFACTOR cycle.

What is the best way to maintain a disciplined commit history during refactoring?

The best way to maintain a disciplined commit history during refactoring is to follow the RED-GREEN-REFACTOR cycle, using conventional commit messages to ensure an auditable history and provide TDD evidence for easier code reviews.

Does TDD workflow integration work with PRs and linting for bug fixes?

Yes, TDD workflow integration works with PRs, tests, and linting to maintain code quality for bug fixes, ensuring that every production change is guided by a clearly failing test before the minimum implementation is applied.

How do I start the Test-Driven Development cycle for a new feature?

To start the Test-Driven Development cycle for a new feature, create a clearly failing test, implement only the minimum code required to pass that test, and then commit the change using conventional commit messages.

What do I need to maintain the RED-GREEN-REFACTOR cycle in my software projects?

To maintain the RED-GREEN-REFACTOR cycle, you need a standard testing framework, clearly failing tests, and conventional commit messages to ensure incremental delivery and auditable history across features, bug fixes, and refactors.

Why should I use a strict Test-Driven Development process for production changes?

You should use a strict Test-Driven Development process for production changes because it is the backbone of safe, maintainable code, providing incremental delivery and TDD evidence that ensures disciplined code quality across software projects.