agentsclimarketplace

Tdd

Skill mrzhangguoguo/oh-my-workbuddy/skills/tdd

1:1 WorkBuddy port of oh-my-codex — 46 catalog-driven skills (30 active + 16 deprecated), bilingual docs.

Install
npx -y skills add mrzhangguoguo/oh-my-workbuddy --skill tdd

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Deprecated TDD shim. Keep test-first discipline inside the active implementation workflow (folded into `plan`).

SKILL.md

1.5 KB, as published. Nobody here has run it

Ported from oh-my-codex tdd. OMX runtime conventions ($macro invocation, omx CLI, .omx/ state directory) are replaced with WorkBuddy idioms (Skill tool, Agent tool, task list, .workbuddy/memory).

TDD — deprecated

Hard-deprecated as a standalone skill. Do not invoke or route this skill.

Keep test-first discipline inside the active implementation workflow (the plan skill and normal implementation flow). The discipline is the value; here it is for reference:

The Iron Law: NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST. Write code before the test? Delete it and start over.

Red-Green-Refactor cycle:

  1. RED — Write the next failing test; run it; it MUST fail. If it passes, the test is wrong.
  2. GREEN — Write only enough code to pass. No extras. Run; it MUST pass.
  3. REFACTOR — Improve quality; run tests after every change; must stay green.
  4. REPEAT — Next failing test.

Enforcement: code-before-test → stop and write the test; test-passes-first → fix it to fail; multiple features per cycle → one test, one feature; skipping refactor → go back and clean up.

For durable multi-goal execution that should keep this discipline, use ultragoal; for the implementation workflow itself, use plan.

Gives 2 of the 12 instructions most tdd skills give

Counted across 439 of the 443 authors here whose files we hold, read 2026-08-06

  • write minimal code to pass the testin 302 of 439, across 218 files
  • write a failing test firstin 176 of 439, across 112 files
  • refactor code only after tests passin 171 of 439, across 101 files
  • watch the test fail before writing codein 142 of 439, across 93 files
  • test one behavior per testin 106 of 439, across 44 files
  • refactor code while keeping tests greenin 99 of 439, across 86 files
  • delete code written before testshere, and in 98 of 439, across 54 files
  • run tests after each refactor stephere, and in 85 of 439, across 54 files
  • Use real code instead of mocks unless unavoidablein 64 of 439, across 21 files
  • confirm the test fails for the right reasonin 64 of 439, across 60 files
  • reproduce bugs with a test before fixingin 53 of 439, across 36 files
  • write tests before implementationin 48 of 439, across 39 files

Said here and by no other author read

  • Do not invoke or route this skill
  • Keep test-first discipline in implementation workflows
  • Test only one feature per cycle
  • Use the plan skill for implementation workflows

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.