Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you encounter any unexpected error. Use when you need a systematic approach to finding and fixing the root cause rather than guessing.
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
# Debugging and Error Recovery
## Overview
Systematic debugging with structured triage. When something breaks, stop adding features, preserve evidence, and follow a structured process to find and fix the root cause. Guessing wastes time. The triage checklist works for test failures, build errors, runtime bugs, and production incidents.
## When to Use
- Tests fail after a code change
- The build breaks
- Runtime behavior doesn't match expectations
- A bug report arrives
- An error appears in logs or console
- Something worked before and stopped working
## The Stop-the-Line Rule
When anything unexpected happens:
```
1. STOP adding features or making changes
2. PRESERVE evidence (error output, logs, repro steps)
3. DIAGNOSE using the triage checklist
4. FIX the root cause
5. GUARD against recurrence
6. RESUME only after verification passes
```
**Don't push past a failing test or broken build to work on the next feature.** Errors compound. A bug in Step 3 that goes unfixed makes Steps 4-10 wrong.
## The Triage Checklist
Work through these steps in order. Do not skip steps.
### Step 1: Reproduce
…
The line at the top of this page pins the label git:20260627.bd6e9ea, 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.
GET https://markdownregistry.com/api/v1/artifacts/art_5hu7cu64oj4zqznm
GET https://markdownregistry.com/api/v1/resolve?ref=hamza-ali-shahjahan/hamzaish/debugging-and-error-recovery
GET https://markdownregistry.com/api/v1/blob/2539c0078466755c192123c34758aa432da5d29529340037113eeaecb6647b0e
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.
hamza-ali-shahjahan/hamzaish · _archive/v0/agents/_orchestrator/SKILL.md · Top-level routing brain. Given any user request, identifies the product + stage + intent, then routes to the right…
hamza-ali-shahjahan/hamzaish · _archive/v0/agents/idea/competitor-mapper/SKILL.md · Map the competitive landscape by tier (direct/indirect/acquirer/adjacent) and argue why each could win. Antidote to…
hamza-ali-shahjahan/hamzaish · _archive/v0/agents/idea/devils-advocate/SKILL.md · Stress-test an idea or hypothesis. Build the strongest possible case AGAINST it, find disconfirming evidence, and…
hamza-ali-shahjahan/hamzaish · _archive/v0/agents/idea/idea-generator/SKILL.md · Generate startup ideas grounded in Hamza's existing patterns, current trends, and validated demand signals. Never just…
hamza-ali-shahjahan/hamzaish · _archive/v0/agents/idea/interview-synthesizer/SKILL.md · Synthesize a batch of customer interviews into evidence-for + evidence-against the hypothesis, with pattern surfacing…
hamza-ali-shahjahan/hamzaish · _archive/v0/agents/idea/problem-sharpener/SKILL.md · Turn vague problem observations into testable hypothesis statements with specific who/when/severity/current-workaround…
addyosmani/agent-skills · skills/debugging-and-error-recovery/SKILL.md · Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke…
shashankswe2020-ux/whoop-mcp · .github/skills/debugging-and-error-recovery/SKILL.md · Guides systematic root-cause debugging. Use when tests fail, builds break, behavior doesn't match expectations, or you…
nota-america/forgecat-agent-profiles · profiles/addyosmani/agent-skills/for-forgecat/platforms/cursor/.cursor/skills/debugging-and-error-recovery/SKILL.md · Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke…
nota-america/forgecat-agent-profiles · profiles/addyosmani/agent-skills/for-forgecat/platforms/codex/.agents/skills/debugging-and-error-recovery/SKILL.md · Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke…
nota-america/forgecat-agent-profiles · profiles/addyosmani/agent-skills/for-codex/.agents/skills/debugging-and-error-recovery/SKILL.md · Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke…
nota-america/forgecat-agent-profiles · profiles/addyosmani/agent-skills/for-forgecat/skills/debugging-and-error-recovery/SKILL.md · Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke…
nota-america/forgecat-agent-profiles · profiles/addyosmani/agent-skills/for-cursor/.cursor/skills/debugging-and-error-recovery/SKILL.md · Guides systematic root-cause debugging. Use when tests fail, builds break, something that worked yesterday broke…