Systematic Debugging

Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.

2,245 stars 418 forksSoftware Development Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add mrgoonie/claudekit-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add mrgoonie/claudekit-skills --skill Systematic Debugging
Manual install
git clone --depth 1 https://github.com/mrgoonie/claudekit-skills.git /tmp/claudekit-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claudekit-skills/.claude/skills/debugging/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)
- Manager 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

2. **Reproduce Consistently**
   - Can you trigger it reliably?
   - What are the exact steps?
Read the full skill on GitHub

Details

Skill name
Systematic Debugging
Path
.claude/skills/debugging/systematic-debugging/SKILL.md
Repo updated
3 April 2026
Copies
Found in 3 GitHub repos

FAQ

What does the Systematic Debugging skill do?

Four-phase debugging framework that ensures root cause investigation before attempting fixes. Never jump to solutions.

How do I install the Systematic Debugging skill?

Claude Code plugin: /plugin marketplace add mrgoonie/claudekit-skills. 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 mrgoonie/claudekit-skills, which has 2,245 GitHub stars and 418 forks.

Related skills

MCP Builder

2.2k

mrgoonie/claudekit-skills

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

AI, LLMs & AgentsIn 2 lists418

PDF

2.2k

mrgoonie/claudekit-skills

Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms. When Claude needs to fill in a PDF form or programmatically process, generate, or analyze PDF documents at scale.

Documents & Office Files418

DOCX

2.2k

mrgoonie/claudekit-skills

Comprehensive document creation, editing, and analysis with support for tracked changes, comments, formatting preservation, and text extraction. When Claude needs to work with professional documents (.docx files) for: (1) Creating new documents, (2) Modifying or editing content, (3) Working with tracked changes, (4) Adding comments, or any other document tasks

Documents & Office Files418

Verification Before Completion

2.2k

mrgoonie/claudekit-skills

Run verification commands and confirm output before claiming success

Software Development418

Defense in Depth Validation

2.2k

mrgoonie/claudekit-skills

Validate at every layer data passes through to make bugs impossible

Software Development418

Architecture Optimization

2.7k

wondelai/skills

Guided journey from a working codebase grown slow and tangled to one measurably fast, cleanly bounded, and readable. Orchestrates eight skills phase by phase - working-with-legacy-code, clean-architecture, software-design-philosophy, refactoring-patterns, system-design, ddia-systems, release-it, pragmatic-programmer - every phase carries its method inline so it runs standalone, asking the user questions at every decision point and recording results in the project docs/ folder (PERFORMANCE.md, ARCHITECTURE.md, ARCHITECTURE-OPTIMIZATION-PLAN.md) so the journey resumes across sessions. Use when t

Software DevelopmentIn 2 lists266

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