systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: wildwasser

Guide software debugging through four mandatory investigation phases before fixes.

35|13|Updated Dec 12, 2025

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

Ready to run

npx skills add https://github.com/wildwasser/opencode-agents --skill systematic-debugging-wildwasser

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined, repeatable approach to diagnosing bugs and unexpected behavior, ensuring root causes are found before fixes.

Core Features & Use Cases

Phase-driven investigation: Enforces a four-phase workflow (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to avoid symptom fixes.
Defensive practices: Includes defense-in-depth patterns and anti-pattern awareness to improve resilience.
Triage and learning: Documents evidence gathering, tracing, and validation to accelerate debugging across real-world scenarios like tests, builds, and production incidents.

Quick Start

Load the skill and begin with Phase 1: Root Cause Investigation; read error messages, reproduce, and collect evidence 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 the best way to find the root cause of a software bug instead of just fixing the symptom?▼

Root-cause debugging requires isolating the actual source of software bugs before proposing fixes. It enforces a four-phase investigation workflow to trace data flow and validate across multiple layers, preventing superficial symptom fixes.

How do I debug a production incident systematically without making rushed code changes?▼

Systematic debugging mandates completing Phase 1: Root Cause Investigation before any implementation. You must read error messages, reproduce the issue, and collect evidence to avoid rushed code changes during production incidents.

Why does my bug fix keep reintroducing the same error in different layers of the system?▼

Skipping root cause investigation often leads to symptom fixes that fail across system layers. Applying defense-in-depth techniques and validating data flow during pattern analysis prevents errors from reappearing in different layers.

What steps should I follow to trace data flow and isolate a failure during integration testing?▼

Trace data flow by gathering evidence and reproducing the failure during Phase 1. Proceed to Pattern Analysis, then Hypothesis & Testing, ensuring you validate across multiple layers before reaching the Implementation phase.

Does systematic debugging work for build failures and test scenarios, or is it only for production incidents?▼

Systematic debugging applies across development, testing, production, and integration scenarios. The disciplined four-phase workflow effectively isolates root causes and guides fixes for build failures and test failures alike.