debug SKILL.md skillA
debug from abdurrafay2004/handoff is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add abdurrafay2004/handoff/debug@git:20260711.bfd3a58Pins git:20260711.bfd3a58 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- abdurrafay2004/handoff
- Path
skills/debug/SKILL.md- Versions recorded
- 5
- Latest version
- git:20260711.bfd3a58, committed Jul 11, 2026
- First version recorded
- Jul 2, 2026
- Size
- 11,309 bytes
- Repository stars
- 5
- License
- MIT
Use when encountering any bug, test failure, unexpected behavior, or performance regression — before proposing any fix. Root-cause discipline plus a feedback-loop method; applies at every tier.
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
# Debug Part of the **Build/Verify** phases — see the `workflow` skill for tiers and sequencing. Random fixes waste time and create new bugs. Quick patches mask underlying issues. **The Iron Law: NO FIXES WITHOUT ROOT-CAUSE INVESTIGATION FIRST.** Use for any technical issue — test failures, production bugs, unexpected behavior, performance problems, build failures, integration issues. Especially when under time pressure, when "just one quick fix" seems obvious, or when previous fixes didn't work. Debugging discipline is tier-independent: a T1 bug still gets a root cause (the process is fast for simple bugs). ## Phase 0 — Read the local context Before exploring, read the nearest `CONTEXT.md` and `.handoff/` state if they exist — a correct mental model of the modules involved beats an hour of tracing. ## Phase 1 — Build a feedback loop **This is the skill; everything else is mechanical.** A **tight** pass/fail signal that goes red on *this* bug is what bisection, hypotheses, and instrumentation all consume. Without one, no amount of staring at code helps. Spend disproportionate effort here. Ways to construct one, roughly in order: …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_nlt4ayks3vs3swvp/c9749016fc010f6e1e94bb402e43846e1ca55b1f8cdd6a8a58aa20dab7f78ee9.json
Then /plugin install debug@markdownregistry-nlt4ayks3vs3swvp in Claude Code. It installs git:20260711.bfd3a58, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add abdurrafay2004/handoff/debug@sha256:c9749016fc010f6eThe line at the top of this page pins the label git:20260711.bfd3a58, 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_nlt4ayks3vs3swvp)
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 abdurrafay2004/handoff/debug 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 debug from somewhere else? Ask it: where did my debug 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 5 versions of this file, between Jul 2, 2026 and Jul 11, 2026, about one every 2 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260711.bfd3a58 latest | 2026-07-11 | bfd3a58 | 11,309 B | A | view · diff |
| git:20260711.46a3400 | 2026-07-11 | 46a3400 | 11,315 B | A | view · diff |
| git:20260702.0ea7c43 | 2026-07-02 | 0ea7c43 | 11,159 B | A | view · diff |
| git:20260702.82cfccf | 2026-07-02 | 82cfccf | 11,003 B | A | view · diff |
| git:20260702.4afacee | 2026-07-02 | 4afacee | 9,723 B | A | view |
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/debug/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 (11309 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
abdurrafay2004/handoff · 5 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_nlt4ayks3vs3swvp GET https://markdownregistry.com/api/v1/resolve?ref=abdurrafay2004/handoff/debug GET https://markdownregistry.com/api/v1/blob/c9749016fc010f6e1e94bb402e43846e1ca55b1f8cdd6a8a58aa20dab7f78ee9
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 abdurrafay2004/handoff
Every file in abdurrafay2004/handoff