systematic-debugging

Guide root-cause debugging through four phases with stop rules.

1|Updated Jan 5, 2026

Search Tags:#debugging #defense-in-depth #root-cause #phase-based #traceback #hypothesis-testing #reproducible-workflow

Ready to run

npx skills add https://github.com/wedsamuel1230/electronic-mcp-server --skill systematic-debugging-wedsamuel1230

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/wedsamuel1230/electronic-mcp-server/tree/main/.github/skills/systematic-debugging
Command: npx skills add https://github.com/wedsamuel1230/electronic-mcp-server --skill systematic-debugging-wedsamuel1230

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined, four-phase approach to debugging that emphasizes finding the root cause before proposing fixes, reducing wasted time on symptomatic patches.

Core Features & Use Cases

Phase 1: Root Cause Investigation — reproduce the issue, collect evidence, and map data flow.
Phase 2: Pattern Analysis — compare with working references and identify differences.
Phase 3: Hypothesis and Testing — formulate a single hypothesis and test it minimally.
Phase 4: Implementation — create failing tests, apply a single fix, and verify outcomes. Use cases include debugging flaky tests, production incidents, and complex bug hunts where the root cause is not obvious.

Quick Start

Load the Systematic Debugging Skill and begin with Phase 1: read errors, reproduce, and gather evidence before proposing any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is a phase-based root cause debugging workflow?▼

Root cause debugging is a four-phase workflow that forces you to reproduce the issue, collect evidence, and map data flow before proposing any fixes, reducing time wasted on symptomatic patches.

How do I debug a production incident systematically?▼

Debug a production incident by following a disciplined investigation workflow: reproduce the issue, analyze patterns against working references, formulate a single hypothesis, and implement the fix with defense-in-depth checks.

Why does my debugging process keep shortcutting to symptomatic patches?▼

Your debugging process likely shortcuts because it lacks explicit stop rules; a systematic approach enforces complete evidence gathering in Phase 1 and pattern analysis before allowing any hypothesis testing or fixes.

What's the best way to debug flaky tests when the root cause isn't obvious?▼

The best way to debug flaky tests is using a hypothesis-driven workflow: compare the failing test with working references to identify differences, then test a single hypothesis minimally before applying a fix.

Can I use hypothesis testing for complex software bug hunts?▼

Yes, hypothesis testing is ideal for complex bug hunts; it requires formulating a single hypothesis, testing it minimally, creating a failing test, and applying a single fix to verify the outcome.

What are the limitations of a phase-based debugging approach?▼

The limitation of this phase-based debugging approach is its strict enforcement; it requires completing the full root cause investigation and pattern analysis phases before proceeding to hypothesis testing, which may slow down simple fixes.