tdd
Skill1 starsChanged 5 months agoMITView on GitHub
Drive a Python change test-first — red/green/refactor, one behavior at a time. Write the failing pytest, watch it fail, write the minimal code to green, then refactor with the test as a net. Use when building new behavior where the spec is clear enough to express as a test. Trigger phrases "do this test-first", "tdd this", "build this with tests first".
194 other projects use a version of this.
Adopted by
Most recently taken up by
- bamlab/flashlighttheir own version, first seen Nov 16, 2026
- 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
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
jaydubya818Skillfigure-it-out
Use when novel or multi-phase work needs an auditable workflow and no narrower playbook fits.
Also in 61 projects that use this
jaydubya818Skillprinciple-minimize-reader-load
Apply when layers, wrappers, or hidden state make simple behavior hard to follow.
Also in 53 projects that use this
- +2 more from The-Vibe-Company
- +6 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
- The-Vibe-Company/quivr★ 40ksame name
- QuivrHQ/quivr★ 40ksame name
- ccusage/ccusage★ 19ksame name
- ryoppippi/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 repository16 other files it gives its agents.
- catchupSkill
- claude-mdSkill
- context-budgetSkill
- db-querySkill
- debug-fixSkill
- eval-agentSkill
- explainSkill
- fix-issueSkill
- incident-ruleSkill
- pr-reviewSkill
- refactorSkill
- secrets-checkSkill
- setup-projectSkill
- shipSkill
- test-writerSkill
- trace-agentSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 187 edited versions we read keep these.
4
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 19
If the ask has several behaviors, list them and do the first — one at a time.
- Distinctive: line 26
GREEN — minimal code: Write the least code that makes the test pass.
- Distinctive: line 30
REFACTOR — clean with the net: Remove duplication, improve names, extract only if it earns its keep (no premature abstraction).
- Distinctive: line 34
Loop or stop: If more behaviors remain, go back to step 1 for the next one.
“Common” is measured: kept by at least 6 in 10 of the 187 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
Trigger: "do this test-first" / "tdd this" / "build this with tests first"
Standing rules: ../_conventions.md.
Design by test. Write the test before the code, one behavior per cycle. Never skip the red step — a test you never saw fail proves nothing. Never write ahead of the current failing test.
Steps
- Pick ONE behavior. State it as a single sentence: given X, when Y, then Z. If the ask has several behaviors, list them and do the first — one at a time.
- RED — write the failing test. A real
pytesttest naming the behavior (test_<behavior>), Arrange-Act-Assert, one assertion. Run it:pytest path/to/test_x.py::test_behavior. Confirm it FAILS, and fails for the right reason (assertion, not an import error). Show the failure. - GREEN — minimal code. Write the least code that makes the test pass. Hardcode if that's genuinely the smallest step — the next test will force generality. Run the test: it passes. Show it green.
- REFACTOR — clean with the net. Remove duplication, improve names, extract only if it earns its keep (no premature abstraction). Re-run the test file after each change; it stays green. No new behavior in this step.
- Loop or stop. If more behaviors remain, go back to step 1 for the next one. Otherwise run the full test file once to confirm all green.
- Report (terse): behaviors covered · tests added · all green (with the run output). Never report green you didn't watch pass.
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.

