agentleFS
clarknova99clarknova99/multi-provider-harness/.agents/skills/test-driven-development/SKILL.md

test-driven-development

Skill1 starsChanged 4 months agoMITView on GitHub

The red-green-refactor discipline — write a failing test first, make it pass with the least code, then refactor, for any non-trivial logic. Use whenever you implement a feature or fix a bug with real logic (calculations, parsing, state machines, data transforms, reducers, models). Covers how to make hard-to-test code testable by extracting logic, and where TDD hands off to integration/UI testing.

190 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

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

  • obraSkill

    diagnosing-superpowers

    Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.

    Also in 19 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

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 180 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
  1. Distinctive:

    Test-first, not test-after.

    line 7
  2. Distinctive:

    Test the logic, at the smallest unit that has behavior: pure functions, parsers, reducers, models, math.

    line 18
  3. Distinctive:

    Prefer pure functions and value types over stateful singletons — they're trivial to drive test-first.

    line 20
  4. Distinctive:

    Avoid tests that hit the real network, prompt for credentials, or need a live GUI in a headless run — they hang the suite.

    line 25

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: Test-driven development (red → green → refactor)

Test-first, not test-after. For any non-trivial logic the failing test comes before the implementation. A test written first catches the off-by-one and the bad-assumption bug before it reaches the UI — that's the whole point.

Be honest about what's actually enforceable: the hard bar is that non-trivial logic ships with tests that genuinely exercise it and pass the verify gate — writing the test first is the recommended way to get there, not a ritual to fake. A model is tempted to emit the test and the code in one shot; that's acceptable only if the test would truly have failed against the old behavior. If a test really arrived after the code, say so rather than back-dating the story.

The loop

  1. RED — write the smallest test that fails for the missing behavior, and run it. Watch it fail for the right reason — a test that passes before you write code is testing the wrong thing.
  2. GREEN — write the least code that makes it pass. No extra generality.
  3. REFACTOR — clean up names/structure with the test green; re-run to stay green. Repeat per behavior, not per feature — several small cycles per task.

What to test / how to make it testable

  • Test the logic, at the smallest unit that has behavior: pure functions, parsers, reducers, models, math.
  • Make it testable by extracting logic out of hard-to-test layers. Logic buried in a UI controller, a request handler, or a main() is not unit-testable; the same logic moved into a plain module/function is. Factor first, then red-green.
  • Prefer pure functions and value types over stateful singletons — they're trivial to drive test-first.

What TDD does NOT cover

  • UI surfaces and end-to-end flows are proven by integration/UI tests, not unit red-green. Extract the logic behind the surface into a testable unit (red-green that), and cover the surface itself with whatever integration/UI test the project uses.
  • Performance/footprint invariants are proven by a targeted benchmark or self-test, not a unit assertion (see verify).
  • Avoid tests that hit the real network, prompt for credentials, or need a live GUI in a headless run — they hang the suite. Use a fake/seam instead.

Verify

The project's verify gate runs the whole suite green before a task commits. A task's diff should show the test and the code it forced; if a test genuinely arrived after the code, say so honestly rather than back-dating the story.

Download now (ZIP)

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.