bug-fix-protocol SKILL.md skillA
bug-fix-protocol from codealive-ai/ai-driven-development is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add codealive-ai/ai-driven-development/bug-fix-protocol@git:20260504.4d670efPins git:20260504.4d670ef in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- codealive-ai/ai-driven-development
- Path
skills/bug-fix-protocol/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260504.4d670ef, committed May 4, 2026
- Size
- 2,600 bytes
- Repository stars
- 163
- License
- MIT
8-step disciplined bug-fix protocol that treats every production bug as two failures — the code defect itself and the testing system that allowed it through. Use when fixing a production bug, investigating a regression, writing a post-mortem, or auditing a missed defect. Triggers on "fix this bug", "production bug", "regression test", "post-mortem", "test gap", "why did the tests miss this".
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
# Bug Fix Protocol A bug fix is **two fixes in one**: fix the code, **and** fix the testing system that let the bug through. Skipping the second step means the same class of bug ships again. The full protocol (philosophy, eight steps with examples, audit checklist, anti-patterns) lives in [`PROTOCOL.md`](PROTOCOL.md). Read it before applying. ## When to apply Use this protocol whenever a defect reaches production, staging, or a customer environment. Do **not** use it for bugs caught locally during normal development — those are part of the writing process, not testing-system failures. ## The eight steps (summary) 1. **Analyze and reproduce requirements.** Understand exact actual vs expected behaviour; identify minimal repro path; ask the user before guessing on ambiguities. 2. **Write a failing test (red).** Encode the bug as a test that fails for the right reason. No code change yet. 3. **Trace root cause.** Walk the failing test back through the system. Stop at the smallest place that, if changed, makes the test pass. 4. **Apply the minimal fix.** Smallest possible change. No drive-by refactors. …
Read the whole file at its exact version.
How to install
mdr add codealive-ai/ai-driven-development/bug-fix-protocol@sha256:1ff10d9c590343b7The line at the top of this page pins the label git:20260504.4d670ef, 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_6ag26bd2y4vdnlmk)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on May 4, 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 (2600 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
codealive-ai/ai-driven-development · 163 stars · license MIT · pushed 2026-10-20 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_6ag26bd2y4vdnlmk GET https://markdownregistry.com/api/v1/resolve?ref=codealive-ai/ai-driven-development/bug-fix-protocol GET https://markdownregistry.com/api/v1/blob/1ff10d9c590343b7ea6c802f8948d1cfcfb51f54827d6642ed45360321072aea
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.