systematic-debugging

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

1.8k|370|Updated Mar 13, 2021

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

Ready to run

npx skills add https://github.com/towardsthecloud/cloudburn --skill systematic-debugging-towardsthecloud

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically debugging helps you identify the root cause of any bug, failure, or unexpected behavior before proposing a fix.

Core Features & Use Cases

Phase-based approach guiding through Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
Anti-patterns and safeguards that discourage symptom fixes and encourage evidence-driven decisions.
Defense-in-depth: multiple validation layers and stack-trace instrumentation to catch issues early.

Quick Start

Examine a failing scenario, follow the four phases, and validate fixes with tests and defensive checks.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is a systematic debugging approach for finding root causes?▼

To debug systematically, follow a four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. This phased approach ensures you validate fixes with tests and defensive checks before deploying them to production.

Why do my bug fixes keep causing new issues in production?▼

Your bug fixes keep causing new issues because they address symptoms rather than root causes. Systematic debugging prevents wasted fixes by enforcing pattern analysis and hypothesis testing, ensuring defensive validation catches the true failure before implementation.

How do I add defensive validation to catch errors early?▼

To add defensive validation, implement defense-in-depth with multiple validation layers and stack-trace instrumentation. This catches issues early during the hypothesis and testing phase before you apply any code patches.

Does this systematic debugging method work for production environments?▼

Yes, this systematic debugging method works for production environments. The four-phase process is explicitly designed to apply across development, testing, and production contexts to investigate failures safely.

What's the best way to stop developers from applying rushed symptom fixes?▼

The best way to stop rushed symptom fixes is to enforce a phased debugging approach with built-in anti-patterns and safeguards. This encourages evidence-driven decisions by requiring pattern analysis and hypothesis testing before implementation.