Builds a requested feature test-first, one behavior at a time, and stops at a diff for review. Use when the user asks for a new function or feature, or says test-first or TDD.
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: write the least code that makes the new test pass, then run the whole test suite and confirm that every test passes. Don't change the tests in this step.
3. Refactor: improve the names and structure of the code you just wrote without changing what it does, and run the tests again. They must still pass.
Repeat until the feature is done, then run the whole test suite and show the diff. Don't commit: the user reviews the diff and commits.
The line at the top of this page pins the label git:20261031.087ca39, 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_w32bvd7zplsabkwx
GET https://markdownregistry.com/api/v1/resolve?ref=wesammustafa/claude-code-everything-you-need-to-know/tdd
GET https://markdownregistry.com/api/v1/blob/cd74dfb9f2d1b98fa647894d8248b2d82fb7dc17c0314ff1c8771f188119f31b
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 · .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…
wesammustafa/claude-code-everything-you-need-to-know · solutions/a-6/team-marketplace/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 · solutions/a-6/team-marketplace/plugins/team-kit/skills/review-checklist/SKILL.md · The team's checklist for reviewing a change to linkcheck. Use before you commit or open a pull request.
wesammustafa/claude-code-everything-you-need-to-know · solutions/a-capstone/dot-claude/skills/team-review/SKILL.md · The team's review of a change to linkcheck, run the same way on a laptop and in CI. Use on a staged diff or a pull…
wesammustafa/claude-code-everything-you-need-to-know · solutions/i-3/dot-claude/skills/changelog/SKILL.md · Adds a one-line entry for the staged changes to CHANGELOG.md. Use when the user asks for a changelog entry.
wesammustafa/claude-code-everything-you-need-to-know · solutions/i-capstone/dot-claude/skills/check-links/SKILL.md · Runs the link checker on a folder and explains each broken link it finds, with the file, the line and a likely fix. Use…
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…
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…
nightly-labs/openbot · marketplace/production-catalog/bundles/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…
