implementing-with-tests SKILL.md skillA
implementing-with-tests from grit-77/done-is-a-claim is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add grit-77/done-is-a-claim/implementing-with-tests@git:20261011.a0f0c71Pins git:20261011.a0f0c71 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- grit-77/done-is-a-claim
- Path
skills/implementing-with-tests/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261011.a0f0c71, committed Oct 11, 2026
- Size
- 3,848 bytes
- Repository stars
- 33
- License
- Apache-2.0
Implement runtime behavior changes and bug fixes with meaningful before-and-after checks, preserved behavior and relevant regression evidence. Use while editing code; prose-only changes do not need a failing test.
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
# Implementing with tests Make the requested behavior observable, change only what it needs, and preserve the surrounding contract. Follow the user's explicit workflow choices; if they override test-first work, record the resulting evidence limits without blocking authorized implementation or pretending a failing baseline was observed. ## Choose the behavior boundary Read the request, current code, relevant callers and existing tests. Identify the behavior to change, inputs and outputs that expose it, and behavior that must remain valid. Respect the assigned files and existing production code. Select a check that distinguishes the requested outcome from a plausible defect. Prefer the real affected boundary when a helper test or mocked success would miss it. Assertions should follow the contract, not repeat implementation constants. Include meaningful edge inputs and relevant preservation checks proportionately. An existing passing test may already cover a preservation requirement or an already implemented outcome. Run and inspect it; add a check only for a real coverage gap. Do not force a failure for behavior that should stay unchanged. …
Read the whole file at its exact version.
How to install
mdr add grit-77/done-is-a-claim/implementing-with-tests@sha256:27549196543f99d3The line at the top of this page pins the label git:20261011.a0f0c71, 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_cml7yxpo7btgu2jg)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 11, 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 (3848 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
grit-77/done-is-a-claim · 33 stars · license Apache-2.0 · pushed 2026-10-22 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cml7yxpo7btgu2jg GET https://markdownregistry.com/api/v1/resolve?ref=grit-77/done-is-a-claim/implementing-with-tests GET https://markdownregistry.com/api/v1/blob/27549196543f99d3c395c7a611de29145e1610a9e3255c0e9d18d12d0457062c
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.