tdd-cycle
Skill209 starsChanged 3 months agoMITView on GitHub
Red-Green-Refactor test-driven development cycle
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Hakkadaikon/hymmetheir own version, first seen Oct 26, 2026
- kitloomlk-stack/testing-debugging-kittheir own version, first seen Oct 15, 2026
- shuvamk/openbenchtheir own version, first seen Jul 2, 2026
- Luis85/agentic-workflowtheir own version, first seen May 9, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- shuvamk/openbench★ 2same name
- Hakkadaikon/hymme★ 0same name
- kitloomlk-stack/testing-debugging-kit★ 0same name
- Luis85/agentic-workflow★ 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 repository16 other files it gives its agents.
- AGENTS.mdAGENTS.md
- backup-skillSkill
- brainstormingSkill
- code-reviewSkill
- content-draftSkill
- cost-analyticsSkill
- daily-standupSkill
- devops-auditSkill
- goal-plannerSkill
- heartbeatSkill
- meeting-minutesSkill
- memory-consolidationSkill
- project-plannerSkill
- research-synthesisSkill
- systematic-debugSkill
- _templateSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 8 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
When implementing any new feature
- Distinctive: line 16
When fixing a bug
- Distinctive: line 17
When refactoring existing code
- Distinctive: line 20
RED: Write a failing test for the desired behavior
- Distinctive: line 21
Verify test fails (confirm test is valid)
- Distinctive: line 22
GREEN: Write minimal code to make the test pass
- Very specific: line 25
Commit with message format: RED|GREEN|REFACTOR: description
- Distinctive: line 29
Delete any code written before tests
- Distinctive: line 30
Never skip the RED phase
“Common” is measured: kept by at least 6 in 10 of the 3 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 Cycle
Description
Enforces the Red-Green-Refactor TDD cycle: write a failing test, make it pass, then refactor. No code is written before a test exists.
When to Use
- When implementing any new feature
- When fixing a bug
- When refactoring existing code
Process
- RED: Write a failing test for the desired behavior
- Verify test fails (confirm test is valid)
- GREEN: Write minimal code to make the test pass
- Verify test passes
- REFACTOR: Clean up code while keeping tests green
- Commit with message format:
RED|GREEN|REFACTOR: description
Rules
- Production code is only written to make a failing test pass
- Delete any code written before tests
- Never skip the RED phase
Agent Assignment
- Primary: opencode
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.