agentleFS
Sign inStart free
HarambeeAIHarambeeAI/bayes-ship/skills/test-driven-development/SKILL.md

test-driven-development

Skill1 starsChanged 7 months agoMITView on GitHub

Enforces RED-GREEN-REFACTOR TDD cycle during implementation. Write the failing test first, watch it fail, write minimal code, watch it pass, commit. Code written before tests must be deleted and restarted. Use when writing any implementation code within the Bayes Ship pipeline.

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

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

  • 0

    Common

    Most of the 178 edited versions we read keep these.

  • 9

    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:

    RED: Write a test that describes the desired behavior.

    line 9
  2. Distinctive:

    GREEN: Write the MINIMUM code to make the test pass.

    line 10
  3. Distinctive:

    If you catch yourself writing implementation before a test: STOP.

    line 16
  4. Distinctive:

    Every test must fail before the implementation exists.

    line 17
  5. Distinctive:

    Testing implementation instead of behavior: Test what the function DOES, not how it does it.

    line 22
  6. Distinctive:

    Tests that never fail: If a test can't fail, it's not a test.

    line 23
  7. Distinctive:

    Giant test setup: If setup is 50 lines and assertion is 1 line, the unit under test is too large.

    line 24
  8. Distinctive:

    Testing private methods: Test the public interface.

    line 25
  9. Distinctive:

    Mocking everything: If you mock the database, the HTTP client, and the filesystem, you're testing that your mocks work, not your code.

    line 26

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

The cycle

  1. RED: Write a test that describes the desired behavior. Run it. Watch it FAIL. If it passes, either the test is wrong or the feature already exists.
  2. GREEN: Write the MINIMUM code to make the test pass. No more. Not "while I'm here" additions. Not "it would be nice to also" extras. The minimum.
  3. REFACTOR: Clean up the code. Extract functions, rename variables, remove duplication. Tests must still pass after refactoring.
  4. COMMIT: One atomic commit. Conventional commit message.

Hard rules

  • If you catch yourself writing implementation before a test: STOP. Delete the implementation. Write the test first. This is non-negotiable in strict mode.
  • Every test must fail before the implementation exists. A test that passes immediately is not testing what you think.
  • "I'll add tests after" is not TDD. It is test-after development and produces weaker tests that verify what was built rather than what was specified.

Anti-patterns to avoid

  • Testing implementation instead of behavior: Test what the function DOES, not how it does it.
  • Tests that never fail: If a test can't fail, it's not a test.
  • Giant test setup: If setup is 50 lines and assertion is 1 line, the unit under test is too large.
  • Testing private methods: Test the public interface. Private methods are implementation details.
  • Mocking everything: If you mock the database, the HTTP client, and the filesystem, you're testing that your mocks work, not your code.

When tdd_mode is relaxed

In relaxed mode, tests may be written after implementation. The RED-GREEN-REFACTOR cycle becomes optional. However, tests must still exist before the task is marked DONE.

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.

Check your setup, free