systematic-debugging

Trace technical bugs to root cause through a four-phase debugging process.

Updated Aug 23, 2026

Search Tags:#debugging #defense-in-depth #triage #root-cause #root-cause-tracing #phase-based-process

Ready to run

npx skills add https://github.com/cptunderpantsmoons/contract-hubv1 --skill systematic-debugging-cptunderpantsmoons

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/cptunderpantsmoons/contract-hubv1/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/cptunderpantsmoons/contract-hubv1 --skill systematic-debugging-cptunderpantsmoons

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps engineers avoid symptom fixes and find root causes quickly, reducing rework and outages.

Core Features & Use Cases

Four-phase framework: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation.
Anti-patterns and defense-in-depth: STOP and re-analyze, add multi-layer validations.
Real-world usage: handles flaky tests, production incidents, and architecture questions.

Quick Start

Log the issue, start Phase 1, and complete root-cause investigation before proposing fixes.

Frequently Asked Questions about systematic-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is root-cause debugging and when do I need a systematic process for it?▼

Root-cause debugging traces issues to their actual source before applying fixes. You need a systematic debugging process to avoid symptom fixes and reduce rework when handling complex technical issues like production incidents or flaky tests.

How do I trace a bug to its root cause before proposing a fix?▼

To trace a bug to its root cause, log the issue and start with a root cause investigation phase. Document evidence, analyze patterns, form hypotheses, and complete this investigation before proposing or applying any fixes.

Can I use this systematic debugging process for production incidents and flaky tests?▼

Yes, systematic debugging applies to production incidents and flaky tests. The framework guides a four-phase process with defense-in-depth checks, ensuring robust, audit-ready debugging for any technical issue you encounter.

What's the best way to validate a bug fix and avoid symptom patches?▼

The best way to validate a bug fix is by validating it with failing tests before implementation. This systematic approach ensures you address the actual root cause and includes defense-in-depth checks to prevent symptom patches.

When should I escalate architectural considerations during root-cause tracing?▼

You should escalate architectural considerations during root-cause tracing when the debugging process reveals deeper systemic issues. The four-phase framework includes escalation steps to handle complex architectural questions that arise during investigation.