test-driven-development SKILL.md skillA

The newest version of a file that held these bytes earlier

test-driven-development in innei/ryugi is at git:20261112.bc75d0f (Nov 12, 2026), graded A.

mdr add innei/ryugi/test-driven-development@git:20261112.bc75d0f

This copy is 3 versions behind it. See what changed · install this older copy instead

This line moves to the next version by itself within about an hour of that file saving one. A copy already installed stays as it is until you update it.

test-driven-development from catherine1401/agent-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
catherine1401/agent-skills
Path
skills/test-driven-development/SKILL.md
Versions recorded
1
Latest version
git:20261021.2dadd08, committed Oct 21, 2026
Size
9,578 bytes
Repository stars
3
License
MIT

Use when implementing any feature or bugfix, before writing implementation code.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Test-Driven Development (TDD)

## Overview

Write the test first. Watch it fail. Write minimal code to pass.

**Core principle:** If you didn't watch the test fail, you don't know if it tests the right thing.

**Violating the letter of the rules is violating the spirit of the rules.**

## When to Use

**Always:**
- New features
- Bug fixes
- Refactoring
- Behavior changes

**Exceptions (ask your human partner):**
- 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

```dot
digraph tdd_cycle {
    rankdir=LR;
    red [label="RED\nWrite failing test", shape=box, style=filled, fillcolor="#ffcccc"];
    verify_red [label="Verify fails\ncorrectly", shape=diamond];
    green [label="GREEN\nMinimal code", shape=box, style=filled, fillcolor="#ccffcc"];
…

Read the whole file at its exact version.

How to install

This older copy, pinned
mdr add catherine1401/agent-skills/test-driven-development@git:20261021.2dadd08

Pins git:20261021.2dadd08 in mdr.lock, 3 versions behind the newest at the top of this page.

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_jjna4b5mikp7pul2/64b03fce4aee5a97a93160cea8111f3ba13a17b7c001db4bd5836d67fd10705d.json

Then /plugin install test-driven-development@markdownregistry-jjna4b5mikp7pul2 in Claude Code. It installs git:20261021.2dadd08, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add catherine1401/agent-skills/test-driven-development@sha256:64b03fce4aee5a97

The older copy line above pins the label git:20261021.2dadd08, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_jjna4b5mikp7pul2.svg)](https://markdownregistry.com/a/art_jjna4b5mikp7pul2)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: get me the newest innei/ryugi/test-driven-development, and what changed since 64b03fc? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of test-driven-development from somewhere else? Ask it: where did my test-driven-development come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on Oct 21, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261021.2dadd08 latest2026-10-21 2dadd08 9,578 BA view

Copies

The newest version, then this copy

Newest: git:20261112.bc75d0f of test-driven-development in innei/ryugi (skills/test-driven-development/SKILL.md), graded A.

This copy: byte for byte that file's version git:20261019.2c789cd, which it committed on Oct 19, 2026, before this repository did; graded A, 3 versions behind.

See what changed since these bytes · ask your agent

Matched on the exact bytes and the commit dates, nothing else. It does not say who wrote the file or where this repository got it.

Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (9578 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

catherine1401/agent-skills · 3 stars · license MIT · pushed 2026-11-02 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_jjna4b5mikp7pul2
GET https://markdownregistry.com/api/v1/resolve?ref=catherine1401/agent-skills/test-driven-development
GET https://markdownregistry.com/api/v1/blob/64b03fce4aee5a97a93160cea8111f3ba13a17b7c001db4bd5836d67fd10705d

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from catherine1401/agent-skills

AGENTS.md AGENTS.md file
catherine1401/agent-skills · AGENTS.md
git:20261006.8297ef6 · audit A · 3 stars
be-ms SKILL.md skill
catherine1401/agent-skills · skills/be-ms/SKILL.md · Draft a message to send to the backend (BE) team about an issue, ready to paste into chat. Use when asked to draft…
git:20261028.fccaf90 · audit A · 3 stars
commit SKILL.md skill
catherine1401/agent-skills · skills/commit/SKILL.md · Prepare focused Git commits when asked to commit or split commits. Never stage unrelated changes or run git commit…
git:20261022.870e460 · audit A · 3 stars
learn SKILL.md skill
catherine1401/agent-skills · skills/learn/SKILL.md · Capture useful lessons from the current session as clear, reusable notes for the user. Use when asked to learn from a…
git:20260925.38de6cb · audit A · 3 stars
ok SKILL.md skill
catherine1401/agent-skills · skills/ok/SKILL.md · Give blanket approval to the agent's latest pending confirmation request, or confirm the agent's latest result worked…
git:20260929.190173f · audit A · 3 stars
quizz SKILL.md skill
catherine1401/agent-skills · skills/quizz/SKILL.md · Convert a multiple-choice question bank with an answer key (PDF, DOCX, or similar) into Wayground (Quizizz) import…
git:20261102.9fed59e · audit A · 3 stars
refactor SKILL.md skill
catherine1401/agent-skills · skills/refactor/SKILL.md · Verify changes against user-level and project-level AGENTS.md and CLAUDE.md rules through an isolated subagent, only…
git:20261006.7b63a26 · audit A · 3 stars
report SKILL.md skill
catherine1401/agent-skills · skills/report/SKILL.md · Create or update a searchable task context handoff when the user asks to report, save context, hand off work, or…
git:20260928.88bc606 · audit A · 3 stars
skill-creator-pj SKILL.md skill
catherine1401/agent-skills · skills/skill-creator-pj/SKILL.md · Create or update an agent skill scoped to a single project's own skill directory (.claude/skills or .codex/skills), not…
git:20260930.e72ab40 · audit A · 3 stars
skill-creator SKILL.md skill
catherine1401/agent-skills · skills/skill-creator/SKILL.md · Create or update an agent skill with appropriately scoped instructions and necessary resources. Use for skills; not…
git:20260927.37d968d · audit A · 3 stars
sync SKILL.md skill
catherine1401/agent-skills · skills/sync/SKILL.md · Two-way sync the current Git branch with its upstream using merge (pull with merge, then push). Use when asked to sync…
git:20261028.23a83e2 · audit A · 3 stars
test SKILL.md skill
catherine1401/agent-skills · skills/test/SKILL.md · After writing or changing code, guide the user through testing the changed behavior. Provide runnable mocks when the…
git:20260927.1c56870 · audit A · 3 stars

Every file in catherine1401/agent-skills

Other files named test-driven-development

test-driven-development SKILL.md skill
obra/superpowers · skills/test-driven-development/SKILL.md · Use when implementing any feature or bugfix, before writing implementation code
git:20260919.5bf4e78 · audit A · 319,649 stars
test-driven-development SKILL.md skill
addyosmani/agent-skills · skills/test-driven-development/SKILL.md · Drives development with tests using the red-green-refactor loop. Use when implementing any logic, fixing any bug, or…
git:20261114.53bd30d · audit A · 119,041 stars
test-driven-development SKILL.md skill
mvschwarz/openrig · skills/_canonical/process/test-driven-development/SKILL.md · Use when implementing any feature or bugfix, before writing implementation code
git:20261025.a37e271 · audit A · 8,889 stars
test-driven-development SKILL.md skill
mvschwarz/openrig · packages/daemon/specs/agents/shared/skills/process/test-driven-development/SKILL.md · Use when implementing any feature or bugfix, before writing implementation code
git:20261025.a37e271 · audit A · 8,889 stars
test-driven-development SKILL.md skill
jnmetacode/superpowers-zh · skills/test-driven-development/SKILL.md · 在实现任何功能或修复 bug 时使用,在编写实现代码之前
v1.9.1 · audit A · 8,551 stars
test-driven-development SKILL.md skill
cbrock84/headcount · plugins/technology/skills/test-driven-development/SKILL.md · Drives implementation by writing a failing test first, then the smallest code that passes it. Use this before writing…
git:20260901.aa45383 · audit A · 2,543 stars
test-driven-development SKILL.md skill
a5c-ai/babysitter · library/methodologies/superpowers/skills/test-driven-development/SKILL.md · Use when implementing any feature or bugfix, before writing implementation code. Enforces RED-GREEN-REFACTOR cycle.
git:20260601.da7723a · audit A · 1,914 stars
test-driven-development SKILL.md skill
a5c-ai/babysitter · library/methodologies/rpikit/skills/test-driven-development/SKILL.md · Test-first development practice where test specifications are written before production code, integrated into plan…
git:20260601.da7723a · audit A · 1,914 stars

Browse by kind, by grade A, or by owner.