Systematic Debugging

4-phase root cause debugging: understand bugs before fixing.

9 stars 2 forksSoftware Development

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Lord1Egypt/RA-Skills --skill systematic-debugging
Manual install
git clone --depth 1 https://github.com/Lord1Egypt/RA-Skills.git /tmp/RA-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/RA-Skills/skills/built-in/software-development/systematic-debugging ~/.claude/skills/systematic-debugging

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Systematic Debugging

## Overview

Random fixes waste time and create new bugs. Quick patches mask underlying issues.

**Core principle:** ALWAYS find root cause before attempting fixes. Symptom fixes are failure.

**Violating the letter of this process is violating the spirit of debugging.**

## The Iron Law

```
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
```

If you haven't completed Phase 1, you cannot propose fixes.

## When to Use

Use for ANY technical issue:
- Test failures
- Bugs in production
- Unexpected behavior
- Performance problems
- Build failures
- Integration issues

**Use this ESPECIALLY when:**
- Under time pressure (emergencies make guessing tempting)
- "Just one quick fix" seems obvious
- You've already tried multiple fixes
- Previous fix didn't work
- You don't fully understand the issue

**Don't skip when:**
- Issue seems simple (simple bugs have root causes too)
- You're in a hurry (rushing guarantees rework)
- Someone wants it fixed NOW (systematic is faster than thrashing)

## The Four Phases

You MUST complete each phase before proceeding to the next.

---

## Phase 1: Root Cause Investigation

**BEFORE attempting ANY fix:**

### 1. Read Error Messages Carefully

- Don't skip past errors or warnings
- They often contain the exact solution
- Read stack traces completely
- Note line numbers, file paths, error codes

**Action:** Use `read_file` on the relevant source files. Use `search_files` to find the error string in the codebase.
Read the full skill on GitHub

Details

Skill name
systematic-debugging
Path
skills/built-in/software-development/systematic-debugging/SKILL.md
Repo updated
17 November 2026

FAQ

What does the Systematic Debugging skill do?

4-phase root cause debugging: understand bugs before fixing.

How do I install the Systematic Debugging skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Lord1Egypt/RA-Skills --skill systematic-debugging. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Systematic Debugging popular?

It lives in Lord1Egypt/RA-Skills, which has 9 GitHub stars and 2 forks.

Related skills

Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.