agentleFS
minglominglo/dsh-skill-superpowers/skills/test-driven-development/SKILL.md

test-driven-development

Skill2 starsChanged 17 days agoLicence not identifiedView on GitHub

Use when implementing any feature or bugfix, before writing implementation code

212 other projects use a version of this, 115 of them edited; 97 of 109 edited versions we compared changed its rules; 17 new projects in the last 4 weeks, against 20 the 4 before.

How people change it

97 of 109 edited versions changed its rules, and some changes recur.

Of the 109 edited versions we compared: 11 keep every rule, 1 is an older text, 97 made changes of their own.

Not in older versions

  1. When writing or changing any test, read [writing-good-tests.md](writing-good-tests.md) for the rules that keep tests honest:missing from 1 of 1
  2. Keep test-only code in test utilities, out of production classesmissing from 1 of 1

Rules people drop

  1. When writing or changing any test, read [writing-good-tests.md](writing-good-tests.md) for the rules that keep tests honest:dropped by 93 of 97
  2. Keep test-only code in test utilities, out of production classesdropped by 93 of 97
  3. No exceptions without your human partner's permission.dropped by 25 of 97
  4. Write code before the test? Delete it. Start over.dropped by 15 of 97
  5. Don't keep it as "reference"dropped by 14 of 97
  6. Don't "adapt" it while writing testsdropped by 14 of 97
  7. Don't look at itdropped by 14 of 97
  8. Keep tests green. Don't add behavior.dropped by 12 of 97

Rules people add

  1. Test-first forces you to see the test fail, proving it actually tests something.added by 78 of 97
  2. No record of what you testedadded by 77 of 97
  3. Delete and rewrite with TDD (high confidence)added by 76 of 97
  4. Keep it and add tests after (low confidence, likely bugs)added by 76 of 97
  5. When adding mocks or test utilities, read @testing-anti-patterns.md to avoid common pitfalls:added by 62 of 97
  6. No exceptions without the user's explicit permission.added by 14 of 97
  7. If you catch yourself doing any of these, delete the code and restart with TDD:added by 12 of 97
  8. Test passes immediately on first runadded by 12 of 97

We split this file and each edited version into the rules they give an agent and match them by wording. A version that adds no rule of its own and has not changed since this file last did reads as an older text, so what it lacks is not counted as dropped. We keep no past texts of a file, so that is inferred, and an edited version that started from an older text still counts its gaps as drops.

Adopted by

Cooling: 17 new projects took it in the last 4 weeks, 0.9× the 4 weeks before.

Week of Sep 20: 5 new projectsWeek of Sep 27: 4 new projectsWeek of Oct 4: 5 new projectsWeek of Oct 11: 6 new projectsWeek of Oct 18: 3 new projectsWeek of Oct 25: 6 new projectsWeek of Nov 1: 6 new projectsWeek of Nov 8: 2 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read.

Most recently taken up by

Used with

Projects with it also use chinese-code-review, chinese-commit-conventions and 9 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.
  • Leodorareluctant259Skill

    chinese-code-review

    中文代码审查规范——在保持专业严谨的同时,用符合国内团队文化的方式给出有效反馈

    Also in 8 projects that use this

  • Leodorareluctant259Skill

    chinese-commit-conventions

    中文 Git 提交规范 — 适配国内团队的 commit message 规范和 changelog 自动化

    Also in 8 projects that use this

  • LLl0k0laDSkill

    using-agent-skills

    Use when starting a session or when you need to discover which skill applies to the current task. This is the meta-skill that governs how all other skills are discovered and invoked.

    Also in 39 projects that use this

  • LLl0k0laDSkill

    git-workflow-and-versioning

    Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.

    Also in 47 projects that use this

  • MrCipherSmithSkill

    constraint-driven-development

    Use when a project needs a persistent, measurable quality bar — starting a project without documented standards, 'set up constraints', or when coverage/perf/a11y thresholds get re-debated per-PR. Produces CONSTRAINTS.md with enforceable numbers, ratchets, and a guard against silent weakening. NOT for throwaway prototypes or a one-off CI setup.

    Also in 15 projects that use this

  • +3 more from Leodorareluctant259
  • +3 more from LLl0k0laD

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. 2 are common, 14 are distinctive, and 0 are very specific to this project.

  • 2

    Common

    Most of the 167 edited versions we read keep these.

  • 14

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

The licence could not be identified — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 167 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.

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.