Skip to content
SkillModel-led737 tokens in use

tdd

Test-first development for coding agents: agree the seams, then one failing test and one minimal fix per slice.

328,764 stars on the repository MIT Licensemattpocock/skills · skills/engineering/tdd
claude plugin install mattpocock-skills@claude-plugins-official
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing tdd costs

33tokens idle
737tokens in use
1,571tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts and code blocks. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure11/25
  • Examples6/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Excellent
  • Development activity96
  • Maintenance100
  • Community56
  • Maturity32
  • Momentum40

The tdd skill is a reference for the red-green loop. It defines what a good test is, where tests go, which anti-patterns to avoid and the rules each cycle follows. It fires when you want to build features or fix bugs test-first, mention red-green-refactor, or ask for integration tests.

It links to companion files on writing tests and on mocking.

What You Get

  • A shared definition of a good test that reads like a specification
  • A confirmed list of seams to test, each with a note on what it catches and misses
  • Named anti-patterns to watch for
  • A loop with clear rules: red before green, one slice at a time

Common Use Cases

  • Build a new feature test-first with an agent
  • Fix a bug by writing a failing test that reproduces it
  • Add integration tests at the public interface of a module

What Makes It Unique

It asks for agreement on test seams before the first test, which focuses effort on critical paths and complex logic. It names tautological tests, where the assertion recomputes the code’s own answer, next to implementation-coupled tests and horizontal slicing, and it keeps refactoring out of the loop and in the review stage.

Under The Hood

A SKILL.md with two linked reference files, tests.md and mocking.md. It reads GLOSSARY.md and ADRs when they exist so test names use the project’s vocabulary, and it can call the codebase-design skill when the shape of an interface is in question. It runs no scripts of its own.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers