code-debug SKILL.md skillA
code-debug from alexeyshishin/as-skill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add alexeyshishin/as-skill/code-debug@git:20261017.66ad76dPins git:20261017.66ad76d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- alexeyshishin/as-skill
- Path
domains/code/skills/code-debug/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261017.66ad76d, committed Oct 17, 2026
- First version recorded
- Aug 8, 2026
- Size
- 1,623 bytes
- Repository stars
- 5
- License
- MIT
Find the root cause of a bug or failing test. Spawns 1 debugger subagent that reproduces, ladders hypotheses, isolates with evidence, and applies the minimal fix. Use when a test fails, /code-build reports blocked, or "X stopped working". Does NOT design features (that's /code-plan).
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
# Skill: /code-debug
ORCHESTRATOR. One debugger subagent. It diagnoses before it touches anything.
## Invocation
`/code-debug "<error text / failing test / what broke>"` (optionally `/code-debug <slug>` to tie it
to a feature build)
## Steps
1. **Gather the symptom**: the error/stack/failing-test name from the user, plus the build
report `swarm-report/<slug>-build.md` if a slug was given.
2. **Spawn 1 debugger** (`Task`, `general-purpose`). Prompt:
> Answer TERSE. Read `.claude/agents/code-debugger.md` and follow it exactly.
> Symptom: <verbatim error / failing test>. Feature slug (if any): <slug>.
3. **Report** the debugger's return verbatim: root cause, evidence, fix, and the
re-run output.
4. **Route the outcome:**
- `fixed` → suggest `/code-review <slug>` to check the fix.
- `root_cause_found` (found but not fixed) or `stuck` → show the hypothesis ladder;
the user decides the fix, or re-run `/code-build <slug>` with the root cause as input.
- `cannot_reproduce` → ask the user for exact repro steps; do not guess-patch.
## Where it sits in the loop
`/code-plan → /code-build → /code-review`. If a test fails or review says `rework` → `/code-debug` →
…Read the whole file at its exact version.
How to install
mdr add alexeyshishin/as-skill/code-debug@sha256:e6e274d2e9fc7c0bThe line at the top of this page pins the label git:20261017.66ad76d, 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_jhowuih4yyj26dud)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Aug 8, 2026 and Oct 17, 2026, about one every 23 days. Its first recorded version is graded C and its latest A.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261017.66ad76d latest | 2026-10-17 | 66ad76d | 1,623 B | A | view · diff |
| git:20260811.6b9321d | 2026-08-11 | 6b9321d | 1,618 B | A | view · diff |
| git:20260809.c3a06fb | 2026-08-09 | c3a06fb | 1,558 B | A | view · diff |
| git:20260808.e616f6d | 2026-08-08 | e616f6d | 0 B | C | 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 (1623 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
alexeyshishin/as-skill · 5 stars · license MIT · pushed 2026-10-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jhowuih4yyj26dud GET https://markdownregistry.com/api/v1/resolve?ref=alexeyshishin/as-skill/code-debug GET https://markdownregistry.com/api/v1/blob/e6e274d2e9fc7c0bb9b957c4acdc90a7ca96337584eaab326b78f290f6d09f50
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 alexeyshishin/as-skill
Every file in alexeyshishin/as-skill