tdd
Skill2 starsChanged 8 months agoApache-2.0View on GitHub
Test-Driven Development — Red/Green/Refactor cycle. Writes failing tests first from a spec, implements minimum code to pass, refactors, then verifies.
194 other projects use a version of this.
Adopted by
Most recently taken up by
- lhotwll217/owner-operatortheir own version, first seen Nov 16, 2026
- philoserf/claude-code-configtheir own version, first seen Nov 15, 2026
- e2b-dev/E2Btheir own version, first seen Nov 15, 2026
- backnotprop/pstacktheir own version, first seen Nov 15, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
- yagizdo/quivertheir own version, first seen Nov 15, 2026
Used with
Projects with it also use capture-learning-tools, design-frontend-dev and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
The-Vibe-CompanySkillcapture-learning-tools
Turn technical conversations, bugs, CI failures, review comments,
Also in 5 projects that use this
The-Vibe-CompanySkilldesign-frontend-dev
Clean Impeccable frontend design skill. Use when the user wants to
Also in 5 projects that use this
tristanphvnSkillketchup-video
Catch the user up like /keel:ketchup, with a short subtitled video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.
Also in 14 projects that use this
jaydubya818Skillfigure-it-out
Use when novel or multi-phase work needs an auditable workflow and no narrower playbook fits.
Also in 54 projects that use this
jaydubya818Skillprinciple-laziness-protocol
Apply when a refactor is adding wrappers or abstractions instead of simplifying.
Also in 45 projects that use this
- +2 more from The-Vibe-Company
- +5 more from jaydubya818
Other versions194 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 194
- mattpocock/skills★ 325ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
- trpc/trpc★ 41ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
- QuivrHQ/quivr★ 40ksame name
- The-Vibe-Company/quivr★ 40ksame name
- ryoppippi/ccusage★ 19ksame name
- ccusage/ccusage★ 19ksame name
- MODSetter/SurfSense★ 17ksame name
- GreyDGL/PentestGPT★ 16ksame name
184 more not listed
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 repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- commit-push-prSkill
- freshSkill
- goSkill
- grillSkill
- investigateSkill
- prove-itSkill
- retroSkill
- saveSkill
- secreviewSkill
- statusSkill
- teamSkill
- techdebtSkill
- test-and-fixSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. 0 are common, 18 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 186 edited versions we read keep these.
18
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 12
Run a full test-driven development cycle for a feature or requirement.
- Distinctive: line 25
Write test cases that define the expected behavior.
- Distinctive: line 27
Test one behavior per test
- Distinctive: line 29
Run the tests. All must fail.
- Distinctive: line 30
If any test passes → something is wrong.
- Distinctive: line 41
Read the failing tests carefully.
- Distinctive: line 42
Write the minimum code to make all tests pass.
- Distinctive: line 43
No gold-plating — if the tests don't require it, don't build it
- Distinctive: line 44
No extra features, no premature abstractions
- Distinctive: line 46
Run the tests. All must pass.
- Distinctive: line 47
If any test still fails → fix the implementation, not the test
- Distinctive: line 48
If a test reveals an implementation design issue → fix the design, keep the test
- Distinctive: line 49
Run lint/check for the language:
- Distinctive: line 68
If no refactoring is needed, say so — don't force changes.
- Distinctive: line 78
Run the full test suite (not just the new tests)
- Distinctive: line 79
Run lint and build checks
- Distinctive: line 80
Check for regressions — did any previously passing test break?
- Distinctive: line 113
When you want tighter, more focused tests than test-after produces
“Common” is measured: kept by at least 6 in 10 of the 186 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 — Red / Green / Refactor
Run a full test-driven development cycle for a feature or requirement. Tests are written before implementation, ensuring the design is driven by the specification rather than the code.
Input: A feature description, requirement, or user story passed as the skill argument.
Phase 1 — RED (Write Failing Tests)
Agent perspective: Tester
- Analyze the feature spec. Identify the behaviors, inputs, outputs, and edge cases it implies.
- Determine the appropriate test framework and file location based on the project:
- Rust:
#[cfg(test)]module ortests/directory,cargo test - Python:
pytestintests/ortest_*.py,pytest -v - Shell: BATS or inline assertion scripts
- Rust:
- Write test cases that define the expected behavior. Each test should:
- Have a descriptive name reflecting the requirement
- Test one behavior per test
- Cover happy path, edge cases, and error conditions
- Run the tests. All must fail.
- If any test passes → something is wrong. Either the feature already exists or the test is not actually testing the new behavior. Stop and report.
- Record which tests were written and what specs they cover.
RED checkpoint: N tests written, all failing. Specs covered: [list]Phase 2 — GREEN (Implement Minimum Code)
Agent perspective: Builder
- Read the failing tests carefully. They are your specification.
- Write the minimum code to make all tests pass. Rules:
- No gold-plating — if the tests don't require it, don't build it
- No extra features, no premature abstractions
- Favor the simplest correct implementation
- Run the tests. All must pass.
- If any test still fails → fix the implementation, not the test
- If a test reveals an implementation design issue → fix the design, keep the test
- Run lint/check for the language:
- Rust:
cargo clippy -- -D warnings - Python:
ruff check - Shell:
shellcheck
- Rust:
GREEN checkpoint: N/N tests passing. Files modified: [list]Phase 3 — REFACTOR (Simplify Without Changing Behavior)
Agent perspective: Simplifier
- Review the implementation from Phase 2 for:
- Duplicated code that can be extracted
- Overly complex conditionals
- Poor naming or unclear structure
- Unnecessary allocations or inefficiencies
- Refactor while keeping all tests green. Run tests after each change.
- If no refactoring is needed, say so — don't force changes.
REFACTOR checkpoint: [changes made or "none needed"]. Tests still passing: YES/NOPhase 4 — VERIFY (Final Gate)
Agent perspective: Verifier
- Run the full test suite (not just the new tests)
- Run lint and build checks
- Check for regressions — did any previously passing test break?
- Behavioral diff: compare the change against the base state
- Produce the final verdict
Output Format
## TDD Report: [Feature]
**Cycle**: RED -> GREEN -> REFACTOR -> VERIFIED
### Red Phase
- Tests written: [N] in [file(s)]
- All failing: YES/NO
- Specs covered: [list]
### Green Phase
- Files modified: [list]
- Tests passing: [X/Y]
- Implementation approach: [brief]
### Refactor Phase
- Changes made: [list or "none needed"]
- Tests still passing: YES/NO
### Verdict: PROVEN / FAILEDWhen to Use
- Starting a new feature where the requirements are clear enough to test
- Implementing a bug fix where you can write the regression test first
- Working on specification-driven code (protocol handlers, validators, parsers)
- When you want tighter, more focused tests than test-after produces
- Any time the user invokes
/tddwith a feature description
When NOT to Use
- Exploratory/prototyping work where requirements are still forming
- Pure refactors with no behavioral change (use Simplifier + Verifier instead)
- Configuration changes, documentation, or CI/CD work
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.

