test-plan SKILL.md skillA
test-plan from haacked/dotfiles is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add haacked/dotfiles/test-plan@git:20260821.de0b8f1Pins git:20260821.de0b8f1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- haacked/dotfiles
- Path
ai/skills/test-plan/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260821.de0b8f1, committed Aug 21, 2026
- First version recorded
- Jun 12, 2026
- Size
- 7,230 bytes
- Repository stars
- 135
- License
- none declared
Generate a GitHub Flavored Markdown manual test plan checklist that focuses on scenarios not covered by existing unit/integration tests. Use when the user wants to create a test plan for a PR or an implementation plan.
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 Plan Generator Generate a manual test plan as a flat GFM checklist. Each item is a single line of the form `- [ ] <Title>: <Step>. <Step>. <Verification>.`. The plan must focus on **end-to-end scenarios that automated unit and integration tests do NOT already cover** — behaviors that emerge from coordination between multiple units, crossings of system boundaries, or stateful interactions that are awkward or expensive to assert in code. Restating what unit tests already verify is wasted reviewer effort. ## Modes - **Branch mode** (default) — analyze the current branch's diff against base - **Plan mode** (`--plan <file>`) — analyze an implementation plan file ## Arguments - `--force` — skip preview and confirmation; save immediately - `--plan <file>` — path to an implementation plan file (skip git analysis, use this file as input) - `--save <path>` — custom output path (default: `.context/test-plan.md`) - `--parent <ref>` — override base detection; diff against `<ref>` instead of the auto-detected PR base Example invocations: - `/test-plan` — generate from current branch diff - `/test-plan --plan ./plans/my-feature.md` — generate from plan file …
Read the whole file at its exact version.
How to install
mdr add haacked/dotfiles/test-plan@sha256:33e3906789d5a322The line at the top of this page pins the label git:20260821.de0b8f1, 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_swrq6zbcyes5e4u7)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jun 12, 2026 and Aug 21, 2026, about one every 18 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260821.de0b8f1 latest | 2026-08-21 | de0b8f1 | 7,230 B | A | view · diff |
| git:20260814.a96876b | 2026-08-14 | a96876b | 7,193 B | A | view · diff |
| git:20260814.48451b6 | 2026-08-14 | 48451b6 | 7,190 B | A | view · diff |
| git:20260724.363c383 | 2026-07-24 | 363c383 | 6,631 B | A | view · diff |
| git:20260612.c16ff80 | 2026-06-12 | c16ff80 | 7,192 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 (7230 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
haacked/dotfiles · 135 stars · license none declared · pushed 2026-11-01 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_swrq6zbcyes5e4u7 GET https://markdownregistry.com/api/v1/resolve?ref=haacked/dotfiles/test-plan GET https://markdownregistry.com/api/v1/blob/33e3906789d5a322c555057f2595625d33cbad53bbbdbe07386fb2609bf54f29
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 haacked/dotfiles
Every file in haacked/dotfiles