Test-Driven Development

by HezaoHezao

Test-Driven Development is a Quality skill for Claude Code, published by HezaoHezao in poirot.

185 stars8 forkson HezaoHezao/poirotAdded 2026/08/11+48% in starsRepository updated 2026/07/28

View source on GitHub Download repo ZIP

agentagent-memoryagent-skillagent-skillsagentic-aiagentsai-agentai-agentsai-codingmemorymemory-systemmulti-agent

Install in seconds

Install Test-Driven Development

Copy Test-Driven Development into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/HezaoHezao/poirot/tree/master/poirot/backend/agents/skill/builtin_skills/core/test-driven-development ~/.claude/skills/test-driven-development

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/HezaoHezao/poirot.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: poirot/backend/agents/skill/builtin_skills/core/test-driven-development/SKILL.md in HezaoHezao/poirot
Installs to: ~/.claude/skills/test-driven-development
Collection: One of 37 skills cataloged from this repository
Category: Quality — 1354 skills

What Test-Driven Development does

A rigorous test-driven development workflow enforcing red-green-refactor cycles: write failing tests first, watch them fail, then write minimal code, and refactor. Ideal for AI coding agents to ensure code quality and prevent untested production code.

Test-Driven Development is cataloged under Quality on DirSkills. Test-Driven Development comes from a repository tagged agent, agent-memory, agent-skill, agent-skills and agentic-ai.

Documentation

README

Excerpt

New features
Bug fixes
Refactoring
Behavior changes

Exceptions (ask the user first):

Throwaway prototypes
Generated code
Configuration files

Thinking "skip TDD just this once"? Stop. That's rationalization.

The Iron Law

NO PRODUCTION CODE WITHOUT A FAILING TEST FIRST

Write code before the test? Delete it. Start over.

No exceptions:

Don't keep it as "reference"
Don't "adapt" it while writing tests
Don't look at it
Delete means delete

Implement fresh from tests. Period.

Red-Green-Refactor Cycle

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Test-Driven Development

What else does HezaoHezao publish alongside Test-Driven Development?
Test-Driven Development is one of 37 skills that DirSkills catalogs from HezaoHezao/poirot, the repository it ships in. Its siblings there include Academic Paper Review, ArXiv Research and Architecture Diagram. Each one is a separate skill with its own page in this directory, installs the same way Test-Driven Development does, and is maintained by HezaoHezao in that same repository. The rest of the collection is listed on the HezaoHezao/poirot page.
How does Test-Driven Development compare to other Quality skills?
Test-Driven Development ranks #1273 by stars among the 1354 Quality skills in this catalog. The most-starred ones next to it are Benchmark, Benchmark Optimization Loop and API Design Patterns. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Test-Driven Development against them. Open each page to compare what they document and how they install.