tdd-loop
Skill1 starsChanged 8 days agoMITView on GitHub
Use when you add or change behavior in code, or fix a bug. Runs the red, green, refactor cycle with a failing test first.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- milad-ahmd/agent-skillstheir own version, first seen Nov 8, 2026
- OrionArchitekton/orion-skillstheir own version, first seen Nov 2, 2026
- michaelalber/ai-toolkittheir own version, first seen Nov 1, 2026
- sbradl/claude-skillstheir own version, first seen Oct 15, 2026
- dagarre00/claude-code-templatetheir own version, first seen Oct 15, 2026
- qyndex/claude-inittheir own version, first seen Oct 13, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- khuynh22/agent-dev-team★ 9same name
- ramboz/jig★ 7same name
- milad-ahmd/agent-skills★ 5same name
- michaelalber/ai-toolkit★ 3same name
- OrionArchitekton/orion-skills★ 2same name
- qyndex/claude-init★ 2same name
- dagarre00/claude-code-template★ 1same name
- itsmuskanagarwal/claude-pack★ 0same name
- sbradl/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- apply-architectureSkill
- bootstrapSkill
- clarify-intentSkill
- code-reviewSkill
- map-workSkill
- plan-workSkill
- releaseSkill
- triageSkill
- write-adrSkill
- write-prSkill
- writing-checkSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 9 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
9
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use when you implement behavior.
- Distinctive: line 10
Follow the red-green-refactor cycle from tdd/index.md.
- Distinctive: line 12
If the feature has an active plan, read its next item that is not blocked first.
- Distinctive: line 16
Write a failing test that describes the desired behavior.
- Distinctive: line 17
Write the smallest amount of production code that makes the test pass.
- Distinctive: line 25
Do not implement without a verified claim.
- Distinctive: line 33
Do not write production code before a failing test exists.
- Distinctive: line 35
Do not skip the failing step.
- Distinctive: line 36
Keep each cycle small.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
TDD loop
Use when you implement behavior.
Follow the red-green-refactor cycle from tdd/index.md.
If the feature has an active plan, read its next item that is not blocked first. After you implement and verify the item, record the real evidence, the commit identifier and the status. Follow feature plans.
Steps
- Write a failing test that describes the desired behavior. Confirm it fails for the right reason.
- Write the smallest amount of production code that makes the test pass.
- Confirm the test passes and existing tests still pass.
- Refactor only while tests are green.
- Repeat for the next behavior.
Rules
- Read claims.md. Do not implement without a verified claim.
- You must not implement a mapped issue in the session that mapped it. A fresh session does that work. See work.md.
- In the refactor step, stay inside the task scope. Do not change unrelated code. Keep every existing test green. Do not limit the refactor to code that a test already executes. When no test checks a behavior that this refactor can change, write a test for that behavior first. That test must pass before you change the code. See stewardship.
- Do not write production code before a failing test exists.
- Tests must prove behavior, not implementation details.
- Do not skip the failing step.
- Keep each cycle small.
See also coding/testing.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.