tdd SKILL.md skillA

tdd from painhardcore/pstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add painhardcore/pstack/tdd@git:20260827.04830a9

Pins git:20260827.04830a9 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: painhardcore/pstack
Path: .opencode/skills/tdd/SKILL.md
Versions recorded: 1
Latest version: git:20260827.04830a9, committed Aug 27, 2026
Size: 3,505 bytes
Repository stars: 12
License: MIT

Use only when the user explicitly asks for TDD, a failing test, or a regression test, OR when the bug has an obvious cheap local test target. Skip when the test path is unclear, expensive, integration-heavy, or not requested.

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

# TDD Bug Fix

When fixing a bug with a clear, cheap test path, make the broken behavior executable before changing production code. The goal is a focused regression test that fails before the fix and passes after it.

Do not force a test when it would be impractical. If the available test would require broad harness setup, brittle mocks, slow end-to-end infrastructure, production-only state, vague reproduction steps, or large unrelated fixture churn, skip adding a new test and use the closest useful verification instead.

## Workflow

1. **Understand the bug.** Identify the intended behavior, current behavior, affected path, and smallest observable reproduction.
2. **Choose the narrowest executable check.** Prefer the closest unit, component, integration, or regression test already used for that codepath. If no practical test path is obvious, do not create one from scratch just to satisfy the workflow.
3. **Write the failing test first.** Add the smallest focused test that would have caught the bug. The test should encode intended behavior, not mirror the current implementation.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add painhardcore/pstack/tdd@sha256:b4df402c414c736b

The line at the top of this page pins the label git:20260827.04830a9, 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.

Badge

[![mdr](https://markdownregistry.com/badge/art_dnpbj6wfodrgnxd4.svg)](https://markdownregistry.com/a/art_dnpbj6wfodrgnxd4)

0 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 1 version of this file, committed on Aug 27, 2026.

version	committed	commit	size	audit
git:20260827.04830a9 latest	2026-08-27	04830a9	3,505 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (3505 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

GitHub

painhardcore/pstack · 12 stars · license MIT · pushed 2026-10-16 · branch master

API

GET https://markdownregistry.com/api/v1/artifacts/art_dnpbj6wfodrgnxd4
GET https://markdownregistry.com/api/v1/resolve?ref=painhardcore/pstack/tdd
GET https://markdownregistry.com/api/v1/blob/b4df402c414c736b82f0c2552b14db66dca2b00a53a9ea19b764093cb1c0e68a

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 painhardcore/pstack

architect SKILL.md skill

painhardcore/pstack · .opencode/skills/architect/SKILL.md · Sketch types, signatures, and module structure before code, then stay in the loop while implementation fills in. Use…