fix-a-bug skillA
fix-a-bug is agent-read markdown (skill) from max-sixty/tend: Write a code fix for a bug. Use before writing any fix, whichever workflow you are running..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Fixing a bug The gates every fix attempt clears, whichever workflow you are running. ## Required skills - Load `/tend-ci-runner:propose-instructions` if the fix edits a skill or instruction file. - Load `/tend-ci-runner:push-commits` before reviewing the fix for a push. ## Reproduce first 1. **Understand the report** — What command was run? What was expected? What actually happened? 2. **Find relevant code** — Search the codebase for the functionality described. 3. **Write a failing test** — Add a test to the appropriate *existing* test file that demonstrates the bug. Don't create new test files. 4. **Run the test** to confirm it fails. Use the test commands from the project's instruction files. Generally, have a failing test before writing a fix. A fix without reproduction evidence is not a conservative fix: report what you established instead. If the test passes, the bug may already be fixed — say so. **Only attempt a fix if all of these hold:** - Bug is clearly reproducible (usually, the test written above fails) - Root cause is understood - Fix is localized (1-3 files changed) - Confident the fix is correct ## Skill text fixes …
Read the whole file at its exact version.
How to install
mdr add max-sixty/tend/fix-a-bug@git:20260924.b3c4ba6mdr add max-sixty/tend/fix-a-bug@sha256:7a6f388513597594Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_7v3ncohcrqgdrpbe)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260924.b3c4ba6 latest | 2026-09-24 | b3c4ba6 | 3,852 B | A | view · diff |
| git:20260918.1ca04b2 | 2026-09-18 | 1ca04b2 | 3,664 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 (3852 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
max-sixty/tend · 39 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7v3ncohcrqgdrpbe GET https://markdownregistry.com/api/v1/resolve?ref=max-sixty/tend/fix-a-bug GET https://markdownregistry.com/api/v1/blob/7a6f38851359759444d61b826d21d56dc10a051115fe67a67c3f4f30c41c3159
Your agent 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.