Cm tdd

Skill tody-agent/codymaster/skills/cm-tdd

Use when implementing any feature or bugfix. Routes to the core Red-Green-Refactor loop, test quality guidance, rationalization handling, examples, or stuck-state recovery.From its SKILL.md

Install

npx -y skills add tody-agent/codymaster --skill cm-tdd

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.

SKILL.md

2.2 KB, 455 tokens by cl100k_base, as published. Nobody here has run it

Test-Driven Development (TDD)

TL;DR

Use when writing or fixing code
Cycle: Red → Green → Refactor
Rule: no production code without a failing test first
Next: cm-execution or cm-code-review

When to Use

new features
bug fixes
refactors
behavior changes

The Iron Law

NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST

Choose the Need

Need to execute the normal TDD loop?
└─ YES → Red-Green-Refactor

Need help designing or reviewing test quality?
└─ YES → Test Quality

Need to counter "skip TDD" rationalizations?
└─ YES → Rationalizations

Need a worked bug-fix example?
└─ YES → Bugfix Example

Are you blocked or unsure how to continue?
└─ YES → Stuck / Debugging

Need	Summary	Load
Normal execution	core TDD loop and verification	`references/red-green-refactor.md`
Test quality	what good tests look like	`references/test-quality.md`
Reinforcement	anti-rationalization guidance	`references/rationalizations.md`
Example	concrete bug-fix walkthrough	`references/bugfix-example.md`
Recovery	how to proceed when stuck	`references/stuck-debugging.md`

Load Rules

Load red-green-refactor.md for normal execution.
Load test-quality.md when designing or reviewing tests.
Load rationalizations.md only when the user or agent is trying to bypass TDD discipline.
Load bugfix-example.md only for coaching or example use.
Load stuck-debugging.md only when blocked.

Non-Negotiables

Watch the test fail before writing production code.
Keep implementation minimal until green.
Refactor only after green.
Re-run verification after each meaningful change.

The Bottom Line

Write the failing test first. Pass it minimally. Refactor only after green.

What ships with it: 5 files

2.7 KB alongside SKILL.md

references/

Gives 3 of the 12 instructions most tdd skills give in 455 tokens

Counted across 594 of the 695 authors here whose files we hold, read 2026-09-06

Write minimal code to pass the testhere, and in 356 of 594, across 332 files
Write a failing test before writing production codehere, and in 240 of 594, across 221 files
Refactor code only after tests passin 184 of 594, across 169 files
Refactor code while keeping tests greenhere, and in 140 of 594, across 133 files
Verify the test fails for the expected reasonin 133 of 594, across 121 files
Run tests after each refactor stepin 108 of 594, across 102 files
Use real code instead of mocks whenever possiblein 97 of 594, across 85 files
Reproduce bugs with a failing test before fixingin 90 of 594, across 81 files
Write tests before implementing codein 88 of 594, across 70 files
Verify the test passes after writing codein 71 of 594, across 61 files
Write one test for one behaviorin 71 of 594, across 63 files
Run the full test suitein 63 of 594, across 56 files

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.