systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Best for Emergency debugging under t…Works with GitHubLow risk
⌘source
- author
@sickn33- language
- Python
★34kstars
5.6kforks
Apr 18, 2026
✦overview.md
Key Features
- ·Enforces root cause investigation before any fixes
- ·Structured four-phase debugging process
- ·Prevents symptom fixes and random patches
- ·Applies to any technical issue or bug
Use Cases
- →Investigating test failures before proposing solutions
- →Debugging production bugs systematically
- →Analyzing unexpected behavior in code
- →Troubleshooting performance problems methodically
Best for
- ✓Emergency debugging under time pressure
- ✓Complex bugs with unclear causes
- ✓Teams preventing rework from quick fixes
Not ideal for
- !One-off script debugging
- !Simple syntax errors with obvious fixes
FAQs
name
systematic-debugging
description
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
risk:unknown
source:community
date_added:2026-02-27
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:
$install
1-click copynpx skills add sickn33/antigravity-awesome-skills --skill systematic-debuggingSafety assessment
★
Clarity score
How clear and easy to understand the SKILL.md instructions are, rated from 1 to 5.
3/ 5
goodMostly clear, but there are still a few confusing or poorly structured parts.
◎
Actionability score
How directly an agent can act on the SKILL.md instructions, rated from 1 to 5.
2/ 5
lowSome hints are present, but an agent still has to guess many steps.