cm-tdd

Enforce a test-first Red-Green-Refactor workflow for features and fixes.

48|23|Updated Mar 17, 2026
One-click install
npx skills add https://github.com/tody-agent/codymaster --skill cm-tdd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cm-tdd
Source: https://github.com/tody-agent/codymaster/tree/main/skills/cm-tdd
Command: npx skills add https://github.com/tody-agent/codymaster --skill cm-tdd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Ensures software changes are guided by tests, preventing regressions and enabling safer, design-conscious development.

Core Features & Use Cases

  • Enforces a test-first workflow: write a failing test before coding, run tests to confirm failure, implement the minimal code to pass, and refactor while keeping all tests green.
  • Supports changes across features, bug fixes, and refactoring with rapid, feedback-driven cycles.
  • Helps teams improve code quality, maintainability, and reliability through disciplined test patterns.

Quick Start

Follow the Red-Green-Refactor cycle: write a failing test, make it pass with minimal code, then refactor.

Frequently Asked Questions about cm-tdd

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

FAQPage Schema
What is test-driven development and how does it prevent regressions?

Test-driven development is a workflow where you write a failing test first, implement minimal production code to pass it, and refactor while keeping tests green, ensuring software changes are guided by tests to prevent regressions.

How do I start practicing the red-green-refactor cycle for bug fixes?

To start the red-green-refactor cycle for bug fixes, write a failing test that reproduces the bug, run tests to confirm failure, implement minimal code to make it pass, then refactor while keeping all tests green.

Can I use test-driven development with any programming language or framework?

Yes, test-driven development applies across any programming language or framework for new features, bug fixes, refactoring, and behavior changes, requiring no specific dependencies to enforce the test-first workflow.

Why does writing tests first improve code maintainability compared to testing after?

Writing tests first improves maintainability by enforcing a feedback-driven cycle that guides design decisions through minimal code implementation, ensuring reliable software delivery and safer refactoring with all tests kept green.

When should I not use a strict test-first workflow for refactoring?

A strict test-first workflow may be unnecessary for trivial behavior changes or pure formatting refactors where the feedback cycle provides no design guidance, though keeping tests green remains essential for preventing regressions.