systematic-debugging

Guide software debugging through four phases from root-cause investigation to implementation.

1|Updated Mar 8, 2024

Search Tags:#testing #debugging #defense-in-depth #process #root-cause #systematic-debugging

Ready to run

npx skills add https://github.com/cpp-for-everything/ORM --skill systematic-debugging-cpp-for-everything

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/cpp-for-everything/ORM/tree/main/.windsurf/skills/systematic-debugging
Command: npx skills add https://github.com/cpp-for-everything/ORM --skill systematic-debugging-cpp-for-everything

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a repeatable, root-cause-first framework to resolve bugs quickly and avoid symptom-focused fixes.

Core Features & Use Cases

Four structured phases (Root Cause Investigation, Pattern Analysis, Hypothesis Testing, Implementation) to guide debugging from symptoms to source.
Built-in anti-patterns and defense-in-depth strategies to prevent regressions and ensure robust fixes.
Techniques like root-cause tracing and evidence-based validation across multiple layers to improve reliability.

Quick Start

Follow Phases 1 through 4 in order to identify root causes before implementing fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is systematic debugging and when should I use it?▼

Systematic debugging is a root-cause-first framework for resolving software bugs, test failures, and production incidents. You should use it to avoid symptom-focused fixes and ensure reliable, repeatable bug resolution.

How do I debug production incidents using root-cause investigation?▼

Debug production incidents by following four structured phases: root-cause investigation, pattern analysis, hypothesis testing, and implementation. This process enforces evidence-based validation across multiple layers before applying fixes.

How do I fix recurring test failures without treating symptoms?▼

Fix recurring test failures by applying root-cause tracing and pattern analysis to identify the underlying source. Hypothesis testing validates the true source before implementation, preventing recurring symptom-focused patches.

Does this debugging process work for performance issues?▼

Yes, this debugging process applies directly to performance issues. It guides investigators through root-cause investigation and evidence-based validation to identify the actual source of performance degradation before implementing fixes.

What is the best way to prevent regressions when fixing bugs?▼

The best way to prevent regressions is applying built-in anti-patterns and defense-in-depth strategies during implementation. This ensures robust fixes are validated across multiple layers after hypothesis testing confirms the root cause.

Why should I not apply fixes before finding the root cause?▼

Applying fixes before finding the root cause leads to symptom-focused patches that often cause regressions. Systematic debugging enforces root-cause investigation and hypothesis testing first to ensure the fix resolves the actual source.