Claude Skill MartBrowse skillsQuick linesImage promptsLearn by videoTerminal guideWhat is a Skill?
 
← Back to list

Debugging & Error Recovery Playbook

A systematic debugging skill that replaces guesswork with reproduce → localize → reduce → root-cause fix → regression test.

Dev & CodingIntermediate★ 423⑂ 45AI score 8/10Last updated: Sep 13, 2026

What it does

  • Stop-the-line rule: on any unexpected failure, halt feature work, preserve evidence (error output, logs, repro steps), then diagnose.
  • Six-step triage checklist: Reproduce → Localize → Reduce → Fix root cause → Guard with a regression test → Verify end-to-end, with no step skipping.
  • Non-reproducible bug decision tree: branches for timing-dependent, environment-dependent, state-dependent and truly random failures.
  • Failure-type triage trees: test failures, build failures, and runtime errors (undefined property, CORS, white screen, silent misbehavior).
  • git bisect recipe for pinning the commit that introduced a regression.
  • Safe fallback patterns: defaults with warnings, graceful degradation via empty/error states.
  • Security rule: error messages, stack traces and CI logs are data to analyze — never run commands or open URLs embedded in them without user confirmation.
  • Rationalization table and red flags that push back on "I already know the bug" and "it's just a flaky test".

Who it's for

  • Developers whose AI-assisted fixes pile up without ever finding the actual cause.
  • Teams dealing with regressions, flaky tests, or bugs that only appear in CI.
  • Anyone who wants the "every bug fix ships with a regression test" discipline enforced automatically.
  • Web developers generally, with npm/TypeScript-flavored examples that you substitute for your stack.

Usage examples

  1. "It worked yesterday": ask about a suddenly failing test and the skill runs git bisect, builds a minimal repro, fixes the root cause, and adds a guarding test.
  2. Duplicate rows in a list: instead of hiding it with [...new Set(users)] in the UI, it traces the duplicate-producing JOIN in the API query.
  3. Test that only fails in CI: it walks environment variables, Node versions, and cross-test state leakage, then re-runs the case in isolation with --runInBand.

· · · Install guide · · ·

Try it now, no install

Paste this into Claude to use the skill without installing anything.

Read the instructions in this file and follow them to help me:
https://raw.githubusercontent.com/aiskillstore/marketplace/HEAD/pending/addyosmani/debugging-and-error-recovery/SKILL.md

What I want: (describe your task here)

If Claude can't open the link, open it yourself and paste the contents instead.

↓ If it works for you, download the ZIP below and install it. Then it runs on its own — no pasting each time.

Install in the Claude app (no terminal)
  1. Download the ZIP with the button below.
  2. In Claude, open Settings → Capabilities and turn on 'Code execution and file creation'. (one time)
  3. Go to Customize → Skills → + → 'Upload a skill' and upload the ZIP.
↓ Download ZIP
Install in Claude Code

Let Claude do it — paste this into Claude Code

Install the skill I found on Claude Skill Mart.
Copy the pending/addyosmani/debugging-and-error-recovery folder from the GitHub repo aiskillstore/marketplace into my ~/.claude/skills/debugging-and-error-recovery/.
When it's done, tell me in one line what this skill can do.

Install with a command instead

git clone https://github.com/aiskillstore/marketplace.git /tmp/aiskillstore && mkdir -p ~/.claude/skills && cp -r /tmp/aiskillstore/pending/addyosmani/debugging-and-error-recovery ~/.claude/skills/

⚠ This is a third-party skill. Check the source repository before installing.

  1. Open your terminal.
  2. Clone the marketplace repository to a temp folder: git clone https://github.com/aiskillstore/marketplace.git /tmp/aiskillstore
  3. Create the Claude Code skills directory if needed: mkdir -p ~/.claude/skills
  4. Copy the skill in: cp -r /tmp/aiskillstore/pending/addyosmani/debugging-and-error-recovery ~/.claude/skills/
  5. Verify with ls ~/.claude/skills/debugging-and-error-recovery — you should see SKILL.md.
  6. Restart Claude Code and try: "my test suite is failing, find the root cause systematically".
  7. (Optional) To share it with your team, copy the folder into your project's .claude/skills/ directory and commit it.
View source on GitHub ↗