tdd SKILL.md skillA
tdd in bastani-inc/atomic is at git:20260925.c0155b5 (Sep 25, 2026), graded A.
mdr add bastani-inc/atomic/tdd@git:20260925.c0155b5This copy is 1 version 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.
tdd from yikart/aitoearn 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
- yikart/aitoearn
- Path
project/aitoearn-backend/.agents/skills/tdd/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260623.e3abc45, committed Jun 23, 2026
- Size
- 4,395 bytes
- Repository stars
- 27,948
- License
- MIT
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
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 ## Philosophy **Core principle**: Tests should verify behavior through public interfaces, not implementation details. Code can change entirely; tests shouldn't. **Good tests** are integration-style: they exercise real code paths through public APIs. They describe _what_ the system does, not _how_ it does it. A good test reads like a specification - "user can checkout with valid cart" tells you exactly what capability exists. These tests survive refactors because they don't care about internal structure. **Bad tests** are coupled to implementation. They mock internal collaborators, test private methods, or verify through external means (like querying a database directly instead of using the interface). The warning sign: your test breaks when you refactor, but behavior hasn't changed. If you rename an internal function and tests fail, those tests were testing implementation, not behavior. See [tests.md](tests.md) for examples and [mocking.md](mocking.md) for mocking guidelines. ## Anti-Pattern: Horizontal Slices …
Read the whole file at its exact version.
How to install
mdr add yikart/aitoearn/tdd@git:20260623.e3abc45Pins git:20260623.e3abc45 in mdr.lock, 1 version behind the newest at the top of this page.
claude plugin marketplace add https://markdownregistry.com/mp/a/art_bxtjl6qeljin4v3v/af059705061156fd4845ddbb736fe92b564118ac5f03551e09ef9e8f6d970638.json
Then /plugin install tdd@markdownregistry-bxtjl6qeljin4v3v in Claude Code. It installs git:20260623.e3abc45, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add yikart/aitoearn/tdd@sha256:af059705061156fdThe older copy line above pins the label git:20260623.e3abc45, 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.
[](https://markdownregistry.com/a/art_bxtjl6qeljin4v3v)
4 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: get me the newest bastani-inc/atomic/tdd, and what changed since af05970? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of tdd from somewhere else? Ask it: where did my tdd 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 Jun 23, 2026.
Watch this file (sign in, one email per new version)
Copies
Newest: git:20260925.c0155b5 of tdd in bastani-inc/atomic (packages/subagents/skills/tdd/SKILL.md), graded A.
This copy: byte for byte that file's version git:20260524.d82da68, which it committed on May 24, 2026, before this repository did; graded A, 1 version 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.
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.
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.
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.
Installed this file, say at .claude/skills/tdd/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4395 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
yikart/aitoearn · 27,948 stars · license MIT · pushed 2026-11-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_bxtjl6qeljin4v3v GET https://markdownregistry.com/api/v1/resolve?ref=yikart/aitoearn/tdd GET https://markdownregistry.com/api/v1/blob/af059705061156fd4845ddbb736fe92b564118ac5f03551e09ef9e8f6d970638
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.