agentleFS
intent-driven-devintent-driven-dev/intent-driven-template/.agents/skills/test-driven-development/SKILL.md

test-driven-development

Skill185 starsChanged 32 days agoMITView on GitHub

Use when implementing a change with test-driven development (TDD): work test-first through focused red-green cycles.

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

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 179 edited versions we read keep these.

  • 8

    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:

    Use the repository's existing test tooling and conventions.

    line 8
  2. Distinctive:

    Write one test before changing implementation code.

    line 18
  3. Distinctive:

    Run the test and confirm it fails because the behaviour is missing, not because the test is broken.

    line 19
  4. Distinctive:

    Write only enough implementation code to pass the failing test.

    line 23
  5. Distinctive:

    Run the test, then run the relevant suite.

    line 24
  6. Distinctive:

    Do not add behaviour without first seeing its test fail.

    line 25
  7. Distinctive:

    Read patterns and anti-patterns when choosing a test shape, writing examples, or deciding whether cases belong together.

    line 36
  8. Distinctive:

    Read collaborators before substituting a dependency.

    line 40

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

Test-Driven Development

Use the repository's existing test tooling and conventions.

One test, one behaviour, one reason to fail. A test name describes that one behaviour; never use joiners such as "and", "or", or "etc." to combine independent outcomes. Multiple assertions are acceptable only when together they establish that same behaviour.

Red

  • Select one observable behaviour from the requirement.
  • Write one test before changing implementation code.
  • Run the test and confirm it fails because the behaviour is missing, not because the test is broken.

Green

  • Write only enough implementation code to pass the failing test.
  • Run the test, then run the relevant suite.
  • Do not add behaviour without first seeing its test fail.

Refactor

  • Refactor only while the relevant suite is green, after completing a red-green slice.
  • Refactor either the tests or the implementation in one pass, not both.
  • Reuse shared setup, teardown, helpers, and parameterized structure when they clarify intent without combining behaviours.
  • Rerun the relevant suite after each refactor pass.

Patterns and anti-patterns

Read patterns and anti-patterns when choosing a test shape, writing examples, or deciding whether cases belong together.

Collaborators

Read collaborators before substituting a dependency. Mock system boundaries, not code owned by the application.

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.