bug-fix-protocol SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
bug-fix-protocol from marin-ai-tech/skillforge is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add marin-ai-tech/skillforge/bug-fix-protocol@git:20261109.d25871dPins git:20261109.d25871d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- marin-ai-tech/skillforge
- Path
packages/server/starter-packs/codealive/skills/bug-fix-protocol/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261109.d25871d, committed Nov 9, 2026
- Size
- 2,600 bytes
- Repository stars
- 3
- License
- a license file GitHub does not identify
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
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ti6hrk2vyiatc3lu/1ff10d9c590343b7ea6c802f8948d1cfcfb51f54827d6642ed45360321072aea.json
Then /plugin install bug-fix-protocol@markdownregistry-ti6hrk2vyiatc3lu in Claude Code. It installs git:20261109.d25871d, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add marin-ai-tech/skillforge/bug-fix-protocol@sha256:1ff10d9c590343b7The line at the top of this page pins the label git:20261109.d25871d, 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_ti6hrk2vyiatc3lu)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in marin-ai-tech/skillforge/bug-fix-protocol since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of bug-fix-protocol from somewhere else? Ask it: where did my bug-fix-protocol come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 1 version of this file, committed on Nov 9, 2026.
Watch this file (sign in, one email per new version)
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/bug-fix-protocol/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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
marin-ai-tech/skillforge · 3 stars · license a license file GitHub does not identify · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ti6hrk2vyiatc3lu GET https://markdownregistry.com/api/v1/resolve?ref=marin-ai-tech/skillforge/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.
More from marin-ai-tech/skillforge
Every file in marin-ai-tech/skillforge