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
Build this test-first, one behavior at a time: $ARGUMENTS
1. Red: write one failing test for the next behavior. Run the tests and confirm that it fails, and fails for the reason you expect. Don't change code outside the tests in this step.
2. Green: TODO
3. Refactor: TODO
Repeat until the feature is done, then run the whole test suite and commit the tests and the code together.
The line at the top of this page pins the label git:20261006.11cadf7, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_lxybpactx6tm37ly
GET https://markdownregistry.com/api/v1/resolve?ref=wesammustafa/claude-code-everything-you-need-to-know/tdd
GET https://markdownregistry.com/api/v1/blob/d56324cd64a01cbf186b0c849bfa4c5784692deeecafb38b0d29eb577e208cce
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.
wesammustafa/claude-code-everything-you-need-to-know · .claude/skills/claude-md-review/SKILL.md · Audit a CLAUDE.md file for the patterns that actually degrade Claude Code's output — vagueness, unnamed files, stale…
wesammustafa/claude-code-everything-you-need-to-know · .github/scripts/fixtures/valid-example-kit/tree/examples/intermediate/01-first-skill/dot-claude/skills/five-whys/SKILL.md · Find the root cause of a bug by asking why five times
wesammustafa/claude-code-everything-you-need-to-know · examples/advanced/06-share-your-setup/plugins/team-kit/skills/onboard/SKILL.md · Explains this repository's shared Claude Code setup to a new teammate, covering what is committed and shared, what…
wesammustafa/claude-code-everything-you-need-to-know · examples/intermediate/01-first-skill/dot-claude/skills/five-whys/SKILL.md · Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix…
cursor/plugins · harness/pstack/claude-code/skills/tdd/SKILL.md · Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious…
cursor/plugins · pstack/skills/tdd/SKILL.md · Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious…
michael-denyer/pstack-claude · plugins/pstack/skills/tdd/SKILL.md · Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious…
rohitg00/pro-workflow · skills/tdd/SKILL.md · Drive a change through a red-green-refactor loop - failing test first, minimal code to pass, then clean up. Use when…
backnotprop/pstack · skills/tdd/SKILL.md · Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious…
