systematic-debugging

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

1|1|Updated Feb 28, 2025

Search Tags:#debugging #defense-in-depth #verification #process #phases #root-cause

Ready to run

npx skills add https://github.com/maskelog/Daegu_bus_flutter_app --skill systematic-debugging-maskelog

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/maskelog/Daegu_bus_flutter_app/tree/main/.cursor/skills/systematic-debugging
Command: npx skills add https://github.com/maskelog/Daegu_bus_flutter_app --skill systematic-debugging-maskelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill guides engineers through systematic debugging to uncover root causes before implementing fixes, reducing wasted time on symptom fixes.

Core Features & Use Cases

Phase-based process (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to ensure thorough analysis.
Defense-in-depth mindset with explicit stop rules to prevent rushing to fixes.
Clear, step-by-step workflows that apply to bugs, test failures, or unexpected behavior across codebases.

Quick Start

Load the skill, read the error, reproduce it consistently, then begin Phase 1 before proposing any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I find the root cause of a bug instead of just fixing symptoms?▼

To find the root cause of a bug, follow a four-phase systematic debugging process: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation. This enforces evidence-based verification before applying fixes.

What is the best way to debug production incidents and test failures systematically?▼

Systematic debugging handles production incidents and test failures by mandating pattern analysis and explicit evidence gathering. It requires reproducing the issue consistently before proposing changes or marking the bug resolved.

How do I start a systematic debugging process for an unexpected codebase behavior?▼

To start systematic debugging, load the process, read the error, and reproduce the unexpected behavior consistently. You must complete Phase 1 Root Cause Investigation and gather explicit evidence before proposing any fixes.

Why does fixing symptoms fail to resolve persistent software engineering defects?▼

Fixing symptoms fails because it bypasses root cause investigation and pattern analysis. Without defense-in-depth validation and explicit evidence-based verification, underlying integration defects remain unresolved.

Can I use systematic debugging for performance problems and integration defects?▼

Yes, systematic debugging applies to any technical issue including performance problems and integration defects. It uses a phase-based process with explicit stop rules to prevent rushing to fixes.

When should I not use symptom-driven fixes for unexpected technical issues?▼

Avoid symptom-driven fixes when facing test failures or production incidents. Rushing to fixes without hypothesis testing and defense-in-depth validation increases wasted time and risks recurring defects.