systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: cookeyholder

Identify and resolve technical issues through a four-phase root-cause debugging workflow.

Updated Apr 9, 2026

Search Tags:#debugging #investigation #defense-in-depth #trace #phases #hypothesis #root-cause

Ready to run

npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill systematic-debugging-cookeyholder

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/cookeyholder/django-devcontainer-template/tree/main/.agent/skills/systematic-debugging
Command: npx skills add https://github.com/cookeyholder/django-devcontainer-template --skill systematic-debugging-cookeyholder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined, four-phase workflow to ensure root-cause investigation before proposing fixes, preventing symptom-only patches.

Core Features & Use Cases

Four-phase framework (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) with explicit stop rules.
Defense-in-depth: multiple validation layers and instrumentation to prevent regression and bypassing analysis.
Real-world applicability for bugs, test failures, production incidents, performance issues, and integration problems.

Quick Start

Read the overview and follow Phase 1 checklist 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 root-cause debugging and how does it prevent symptom-only patches?▼

Root-cause debugging is a disciplined workflow enforcing evidence gathering, pattern analysis, hypothesis testing, and implementation before proposing fixes. It prevents symptom-only patches by requiring thorough investigation and defense-in-depth validation layers to ensure the actual cause is resolved.

How do I debug production incidents without applying quick fixes?▼

To debug production incidents without quick fixes, follow a four-phase workflow: gather evidence first, analyze patterns, test hypotheses, and then implement. Explicit stop rules and defense-in-depth instrumentation prevent premature patching and regression.

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

Yes, you can use systematic debugging for performance problems and integration issues. The four-phase root-cause investigation approach applies to any technical issue, including test failures and production bugs, ensuring comprehensive pattern analysis and hypothesis testing.

What's the best way to investigate test failures and find the root cause?▼

The best way to investigate test failures is using a phased root-cause debugging workflow. Start with evidence gathering in Phase 1, move to pattern analysis, test hypotheses in Phase 3, and implement fixes in Phase 4 with defense-in-depth validation.

When should I avoid quick fixes and enforce a debugging workflow instead?▼

You should enforce a debugging workflow instead of quick fixes whenever facing complex bugs, production incidents, or integration issues. Applying systematic root-cause investigation with explicit stop rules ensures regression prevention and validates hypotheses before implementation.

How does hypothesis testing work in a root-cause debugging workflow?▼

Hypothesis testing in root-cause debugging works by validating proposed explanations during Phase 3, after gathering evidence and analyzing patterns. This phase enforces explicit stop rules and defense-in-depth checks before moving to implementation, preventing unverified patches.