systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: wsxwj123

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

7|Updated Jan 27, 2026

Search Tags:#debugging #validation #defense-in-depth #tracing #phases #root-cause

Ready to run

npx skills add https://github.com/wsxwj123/opencode-skills-backup --skill systematic-debugging-wsxwj123

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined, phase-driven framework to diagnose and fix bugs by prioritizing root-cause analysis over quick symptom fixes, reducing wasted effort and rework.

Core Features & Use Cases

Four mandatory phases (Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, Implementation) with explicit checkpoints to prevent skipping steps.
Anti-pattern guidance and defense-in-depth techniques that help teams resist pressure-induced shortcuts and validate fixes across multiple layers.
Practical tooling and tactics, including backward tracing, data-flow validation, and pre-defined testing approaches to ensure robust, repeatable outcomes.

Quick Start

Load this skill and complete Phase 1 before attempting any fix, then follow Phases 2–4 to confirm root cause and a robust resolution.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

Why do my bug fixes keep causing new issues instead of resolving the original problem?▼

Your bug fixes likely address symptoms rather than root causes. Systematic debugging enforces a four-phase root-cause investigation workflow, requiring evidence gathering and pattern analysis before proposing any fixes to prevent recurring issues and rework.

How do I systematically trace a bug back to its root cause?▼

To systematically trace a bug, use backward tracing and data-flow validation. This approach enforces completing a root cause investigation phase to gather evidence and analyze patterns before forming hypotheses, ensuring fixes target the actual defect.

What is the best way to prevent taking debugging shortcuts under tight project deadlines?▼

The best way to prevent debugging shortcuts is applying defense-in-depth techniques with explicit phase checkpoints. This framework provides anti-pattern guidance to resist pressure-induced shortcuts, ensuring thorough hypothesis testing and validation before implementation.

When should I not use a quick fix for a software defect?▼

You should avoid quick fixes whenever a defect requires deep root-cause analysis. If the failure mode involves complex data-flow issues, bypassing the structured investigation and validation phases risks introducing fragile patches and exacerbating the problem.

Can I start implementing a fix before completing the initial debugging phases?▼

No, you cannot implement fixes before completing the initial investigation. The systematic debugging workflow explicitly requires finishing the root cause investigation phase first to validate evidence and prevent skipping critical diagnostic steps.

Does a phase-driven debugging approach work for complex software engineering defects?▼

A phase-driven debugging approach works well for complex defects by applying pattern analysis and validation across multiple layers. It ensures robust, repeatable outcomes by integrating defense-in-depth techniques and predefined testing approaches.