pitroom-tdd SKILL.md skillA
pitroom-tdd from atastech/pitroom is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add atastech/pitroom/pitroom-tdd@git:20260930.2722b16Pins git:20260930.2722b16 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- atastech/pitroom
- Path
skills/pitroom-tdd/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260930.2722b16, committed Sep 30, 2026
- First version recorded
- Sep 30, 2026
- Size
- 9,224 bytes
- Repository stars
- 28
- License
- MIT
Use when you want to drive a feature or bugfix test-first - red, green, refactor, for you and for the workers you brief.
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.**
Workers follow it too: an implementer worker on a plan task is told to use TDD and to report RED and GREEN evidence. Check that evidence in its report before you trust the tests.
## 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.
## 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.
## Red-Green-Refactor
```dot
digraph tdd_cycle {
rankdir=LR;
red [label="RED\nWrite failing test", shape=box, style=filled, fillcolor="#ffcccc"];
…Read the whole file at its exact version.
How to install
mdr add atastech/pitroom/pitroom-tdd@sha256:2e4f943a8cdf9288The line at the top of this page pins the label git:20260930.2722b16, 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_2vz2h23am6dcyuar)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, all committed on Sep 30, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260930.2722b16 latest | 2026-09-30 | 2722b16 | 9,224 B | A | view · diff |
| git:20260930.4470638 | 2026-09-30 | 4470638 | 9,246 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 (9224 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
atastech/pitroom · 28 stars · license MIT · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2vz2h23am6dcyuar GET https://markdownregistry.com/api/v1/resolve?ref=atastech/pitroom/pitroom-tdd GET https://markdownregistry.com/api/v1/blob/2e4f943a8cdf9288f91d11cbf9d9e12ab48d8cb0c43cef30634765379d59d017
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.