home / Coding / Debugging And Error Recovery Skill by @sickn33

Debugging And Error Recovery Skill by @sickn33

FREE

github stars★ 48,690updatedOct 2026repo@sickn33

activity (commits, last 6 months)

6mo ago0

this month1

$git clone https://github.com/sickn33/agentic-awesome-skills

The skill is the skills/debugging-and-error-recovery folder inside that repository. Copy it into the folder your agent loads skills from; check your agent's documentation for where that is.

about Debugging And Error Recovery Skill by @sickn33

Guides systematic root-cause debugging.

our take

A systematic approach to debugging: a stop-the-line rule when something breaks, a triage checklist, and a first step of reproducing the problem before changing code. It applies to failing tests, broken builds and unexpected behaviour.

when to use it

A test or build fails and the cause is unclear
You want an agent to reproduce a bug before it patches
You need a repeatable triage routine for a team

before you install

It slows the first minutes on purpose, which is wasted on obvious typos
Related to the Systematic Debugging skill here, so choose one routine to avoid conflicting advice

what's inside

The original SKILL.md is organised into these sections:

Overview
When to Use
The Stop-the-Line Rule
The Triage Checklist
Step 1: Reproduce
Step 2: Localize
Step 3: Reduce
Step 4: Fix the Root Cause
Step 5: Guard Against Recurrence
Step 6: Verify End-to-End
Error-Specific Patterns
Test Failure Triage

source and license

Written and maintained by @sickn33. It is published under the MIT license, which allows reuse with attribution. SkillDirectory does not claim authorship: this page adds our own review and links back to the original, and the skill's text belongs to its author.

View the full SKILL.md on GitHub ↗

Read the opening of the original SKILL.md

# 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
```
…

Excerpt only, quoted from the author's repository. Open the repository for the complete file.

↓ download .zip