test-driven-implementation SKILL.md skillA
test-driven-implementation from revantark/alan is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add revantark/alan/test-driven-implementation@git:20261020.04de38dPins git:20261020.04de38d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- revantark/alan
- Path
.alan/skills/execute/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261020.04de38d, committed Oct 20, 2026
- Size
- 3,472 bytes
- Repository stars
- 20
- License
- MIT
Implement features with comprehensive tests (unit + integration), verify end-to-end, keep code concise with WHY comments, cover blast area, and clearly report manual test steps and coverage gaps. Use when the user asks you to implement, fix, or extend code and expects rigorous test coverage and verification.
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 Implementation Skill ## When to use - User asks you to implement, fix, refactor, or extend code. - User expects tests, verification, and clear reporting of what is/isn't covered. - User cares about blast-radius safety and manual-test handoff. ## Core conventions (follow all of them) ### 1. Plan before writing code - Restate the request in 1–3 lines. - List assumptions and open questions explicitly. - Identify the **blast area** before touching code (see §6). - Only ask the user when ambiguity is truly blocking; otherwise proceed with a documented assumption. ### 2. Concise implementation - Write the smallest correct change that satisfies the requirement. - No speculative abstractions, no dead code, no "just in case" helpers. - Prefer editing existing functions over adding parallel ones. - Do **not** reformat unrelated code, rename unrelated symbols, or "clean up" outside the blast area. ### 3. Comments = WHY, not WHAT - Every non-trivial comment answers *why* (constraint, tradeoff, invariant, gotcha). - Never narrate *what* the code already says (e.g., `// increment i`). …
Read the whole file at its exact version.
How to install
mdr add revantark/alan/test-driven-implementation@sha256:30674a4aab22b059The line at the top of this page pins the label git:20261020.04de38d, 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_diaavendi6jc7hlz)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 20, 2026.
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 (3472 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
revantark/alan · 20 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_diaavendi6jc7hlz GET https://markdownregistry.com/api/v1/resolve?ref=revantark/alan/test-driven-implementation GET https://markdownregistry.com/api/v1/blob/30674a4aab22b0598200865b336fd871671bfc6082ee962a80d16cb6629997b4
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.