test-driven-development SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
test-driven-development from khaledsaeed18/dotclaude is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add khaledsaeed18/dotclaude/test-driven-development@git:20260921.3a2f779Pins git:20260921.3a2f779 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- khaledsaeed18/dotclaude
- Path
skills/engineering/test-driven-development/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260921.3a2f779, committed Sep 21, 2026
- First version recorded
- Jun 9, 2026
- Size
- 6,938 bytes
- Repository stars
- 5
- License
- MIT
Implement a feature or bugfix test-first using the red-green-refactor cycle. Write a failing test, watch it fail, write the minimal code to pass, then clean up. Works in any language or test runner. Use when building new behaviour or fixing a bug and you want the test to actually prove the code works.
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
Write the test before the code, watch it fail, then write only enough code to make it pass. The point of seeing it fail first is simple: a test you never watched fail might be testing nothing. Tests written after the fact pass immediately, and a test that has only ever passed proves nothing about whether it would catch the bug. ## The one rule **No production code without a failing test that demands it.** If you wrote the implementation first, the honest move is to delete it and start from the test: not keep it "as reference" and reconstruct it, which is just testing-after wearing a costume. Implement fresh from what the test asks for. Exceptions worth asking the user about: throwaway prototypes, generated code, pure config. Everything else (features, bugfixes, behaviour changes) goes test-first. The thought "I'll skip TDD just this once" is the rationalisation this skill exists to catch. ## Where the test goes: seams …
Read the whole file at its exact version.
How to install
mdr add khaledsaeed18/dotclaude/test-driven-development@sha256:cff04a4e4e823961The line at the top of this page pins the label git:20260921.3a2f779, 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_lvxf7rnwl7zoi3jm)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 9, 2026 and Sep 21, 2026, about one every 26 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260921.3a2f779 latest | 2026-09-21 | 3a2f779 | 6,938 B | A | view · diff |
| git:20260921.6c17ffd | 2026-09-21 | 6c17ffd | 6,646 B | A | view · diff |
| git:20260921.36d6832 | 2026-09-21 | 36d6832 | 6,714 B | A | view · diff |
| git:20260704.197b44e | 2026-07-04 | 197b44e | 6,717 B | A | view · diff |
| git:20260609.13bdd5a | 2026-06-09 | 13bdd5a | 5,068 B | A | view |
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 (6938 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
khaledsaeed18/dotclaude · 5 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_lvxf7rnwl7zoi3jm GET https://markdownregistry.com/api/v1/resolve?ref=khaledsaeed18/dotclaude/test-driven-development GET https://markdownregistry.com/api/v1/blob/cff04a4e4e8239613bf5ce00bfa5cb69e978ba98fc9e72ba6b0062d013feb49c
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 khaledsaeed18/dotclaude
Every file in khaledsaeed18/dotclaude