test-driven-development SKILL.md skillA

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

Install it, pinned
mdr add innei/ryugi/test-driven-development@git:20261112.bc75d0f

Pins git:20261112.bc75d0f in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
innei/ryugi
Path
skills/test-driven-development/SKILL.md
Versions recorded
4
Latest version
git:20261112.bc75d0f, committed Nov 12, 2026
First version recorded
Oct 19, 2026
Size
7,837 bytes
Repository stars
524
License
a license file GitHub does not identify

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.

**Before the first edit:** ryugi:using-git-worktrees decides where the
work happens, unless ryugi:executing-specs already did at its Setup.

## 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.

No exceptions without your human partner's permission.

## Red-Green-Refactor

RED: write a failing test → verify it fails correctly → GREEN: minimal
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2zq4h3hk3dae2mcn/d265d67b5214de5fe3ba58611e4e2baaae7a6c5cbc0a1b97f91bb871743148d6.json

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

The exact contents, by fingerprint
mdr add innei/ryugi/test-driven-development@sha256:d265d67b5214de5f

The line at the top of this page pins the label git:20261112.bc75d0f, 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_2zq4h3hk3dae2mcn.svg)](https://markdownregistry.com/a/art_2zq4h3hk3dae2mcn)

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: what changed in innei/ryugi/test-driven-development since the version I have? 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 4 versions of this file, between Oct 19, 2026 and Nov 12, 2026, about one every 8 days.

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

versioncommittedcommitsizeaudit
git:20261112.bc75d0f latest2026-11-12 bc75d0f 7,837 BA view · diff
git:20261027.20888332026-10-27 2088833 12,696 BA view · diff
git:20261027.eb2c3982026-10-27 eb2c398 9,719 BA view · diff
git:20261019.2c789cd2026-10-19 2c789cd 9,578 BA view

Copies

Copies in other repositories

1 file in 1 other repository holds the exact bytes of one of this file's versions, each committed after this file had them: it holds an older version.

A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.

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 (7837 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

innei/ryugi · 524 stars · license a license file GitHub does not identify · pushed 2026-11-17 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_2zq4h3hk3dae2mcn
GET https://markdownregistry.com/api/v1/resolve?ref=innei/ryugi/test-driven-development
GET https://markdownregistry.com/api/v1/blob/d265d67b5214de5fe3ba58611e4e2baaae7a6c5cbc0a1b97f91bb871743148d6

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 innei/ryugi

writing-skills SKILL.md skill
innei/ryugi · .claude/skills/writing-skills/SKILL.md · Use when creating new skills, editing existing skills, or verifying skills work before deployment
git:20261027.2088833 · audit A · 524 stars
AGENTS.md AGENTS.md file
innei/ryugi · AGENTS.md
git:20261117.27b21bf · audit A · 524 stars
artifacts SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-artifacts-single-entry-full/inputs/baseline-skill/SKILL.md · Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click…
git:20261113.586f356 · audit A · 524 stars
artifacts SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-artifacts-single-entry-full/inputs/candidate-skill/SKILL.md · Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click…
git:20261113.586f356 · audit A · 524 stars
artifacts SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-artifacts-slim/skills/baseline/SKILL.md · Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click…
git:20261112.aa9f450 · audit A · 524 stars
artifacts SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-artifacts-slim/skills/candidate/SKILL.md · Use when seeing decides faster than reading — UI directions or mockups to choose between, a page to tune or click…
git:20261112.aa9f450 · audit A · 524 stars
brainstorming SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-brainstorming-slim/skills/baseline/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, modifying…
git:20261112.baa5cf8 · audit A · 524 stars
brainstorming SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-brainstorming-slim/skills/candidate/SKILL.md · You MUST use this before any creative work - creating features, building components, adding functionality, modifying…
git:20261112.baa5cf8 · audit A · 524 stars
executing-specs SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-executing-specs-slim/skills/baseline/SKILL.md · Use when an approved spec or design document is ready to implement and your human partner chose inline execution, or…
git:20261112.e34ce62 · audit A · 524 stars
executing-specs SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-executing-specs-slim/skills/candidate/SKILL.md · Use when an approved spec or design document is ready to implement and your human partner chose inline execution, or…
git:20261112.e34ce62 · audit A · 524 stars
systematic-debugging SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-systematic-debugging-slim/skills/baseline/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
git:20261112.7f08ac0 · audit A · 524 stars
systematic-debugging SKILL.md skill
innei/ryugi · docs/ryugi/skill-evals/2026-11-13-systematic-debugging-slim/skills/candidate/SKILL.md · Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
git:20261112.7f08ac0 · audit A · 524 stars

Every file in innei/ryugi

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.