systematic-debugging

Diagnose software bugs through a four-phase root-cause investigation workflow.

Updated Jan 2, 2026

Search Tags:#debugging #anti-patterns #troubleshooting #defense-in-depth #phases #root-cause

Ready to run

npx skills add https://github.com/2725244134/dotfiles --skill systematic-debugging-2725244134

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/2725244134/dotfiles/tree/main/opencode/.config/opencode/skill/systematic-debugging
Command: npx skills add https://github.com/2725244134/dotfiles --skill systematic-debugging-2725244134

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the tendency to patch symptoms without understanding root causes. It mandates a structured, four-phase approach to debugging, ensuring issues are diagnosed and verified before any fix is proposed.

Core Features & Use Cases

Mandatory four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation, with a rule to complete Phase 1 before fixes.
Anti-patterns and defenses: Explicit guidance on avoiding shortcuts and adopting defense-in-depth practices.
Reference materials: Linked techniques like root-cause-tracing and defense-in-depth to support deep investigations.
Real-world impact: Designed to reduce time spent on thrashing and improve fix quality across complex systems.

Quick Start

Load the skill, read the overview, then execute Phase 1 through Phase 4 in order. If tempted to skip a phase, revisit the phase instructions and anti-patterns. Complete all phases to ensure a robust root-cause fix and durable system behavior.

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 software bug before applying a fix?▼

Root cause debugging requires completing a mandatory investigation phase before fixes, analyzing patterns and testing hypotheses to ensure you resolve the underlying issue rather than patching symptoms.

What is the best way to debug production incidents across multi-component environments?▼

Debugging production incidents benefits from a structured four-phase workflow: root cause investigation, pattern analysis, hypothesis testing, and implementation, ensuring comprehensive diagnosis across complex systems.

Why do my bug fixes keep recurring or causing new issues in complex systems?▼

Recurring bugs typically result from skipping root cause investigation and applying symptom patches. A structured debugging workflow with anti-pattern checks and defense-in-depth validations prevents incomplete fixes.

How do I stop symptom patching and enforce a structured troubleshooting process?▼

Enforce structured troubleshooting by following a mandatory four-phase workflow that requires completing root cause investigation before proceeding to pattern analysis, hypothesis testing, and implementation.

Can I use this systematic debugging approach for test failures and production incidents?▼

Systematic debugging applies to software bugs, test failures, and production incidents across multi-component environments, using defense-in-depth validations to ensure durable system behavior after fixes.

What are common anti-patterns in root-cause debugging that I should avoid?▼

Common debugging anti-patterns include skipping investigation phases, patching symptoms without understanding root causes, and neglecting defense-in-depth validations, all of which lead to thrashing and poor fix quality.