systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: discountedcookie

Diagnose root causes of bugs through a four-phase investigation process.

Updated Oct 26, 2025

Search Tags:#debugging #investigation #diagnostics #phases #root-cause

Ready to run

npx skills add https://github.com/discountedcookie/10x-mapmaster --skill systematic-debugging-discountedcookie

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/discountedcookie/10x-mapmaster/tree/main/.opencode/skills/systematic-debugging
Command: npx skills add https://github.com/discountedcookie/10x-mapmaster --skill systematic-debugging-discountedcookie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces a four-phase debugging approach to diagnose issues before proposing fixes.

Core Features & Use Cases

Four phases: Root cause, pattern analysis, hypothesis testing, and implementation.
Evidence-driven: Requires reproducible steps, logs, and data before changes.
Open-ended guidance: Helps structure debugging discussions and decisions.

Quick Start

When a bug appears, begin with Phase 1: Root Cause Investigation, gather steps to reproduce, and document evidence before proposing changes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I diagnose the root cause of a bug instead of just applying a quick fix?▼

Root cause diagnosis requires a structured four-phase approach: investigate to gather reproducible steps and logs, analyze patterns in the evidence, hypothesize the underlying issue, and only then implement a fix. This prevents recurring bugs and reveals systemic problems rather than symptoms.

What's the best way to approach debugging when I don't know where to start?▼

Begin with Phase 1: Root Cause Investigation. Document exact steps to reproduce the issue, collect diagnostic logs at component boundaries, and gather evidence before proposing any changes. This phase gates all subsequent work and ensures you're solving the actual problem.

Why should I gather logs and reproducible steps before fixing a bug?▼

Evidence-driven debugging prevents guesswork and false fixes. Reproducible steps and diagnostic logs reveal patterns across your codebase and environments, expose root causes rather than surface symptoms, and enable test-driven verification that your fix actually resolves the issue.

Can I skip to implementation if I think I know what's wrong?▼

No. The four-phase process enforces strict gating between investigation and implementation. Skipping to fixes without evidence gathering and hypothesis testing typically addresses symptoms, leaving root causes unresolved and bugs recurring across your codebase.

How do I know when I've finished investigating and can move to the next phase?▼

You've completed investigation when you have reproducible steps, diagnostic logs from component boundaries, and sufficient evidence to form a testable hypothesis. Phase gating ensures you don't advance until each stage is complete, reducing rework and false fixes.