systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: Sulhi

Identify and resolve software bugs through a four-phase root-cause debugging workflow.

Updated Dec 20, 2025

Search Tags:#debugging #documentation #quality-assurance #root-cause #phased-workflow #evidence-gathering

Ready to run

npx skills add https://github.com/sulhicmz/jasaweb --skill systematic-debugging-sulhicmz

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined workflow to identify root causes before proposing fixes, eliminating guesswork and reducing firefighting during software issues.

Core Features & Use Cases

Four-phase debugging process (Phase 1: Root Cause Investigation, Phase 2: Pattern Analysis, Phase 3: Hypothesis & Testing, Phase 4: Implementation)
Emphasizes evidence gathering, traceability, and reproducibility across components and environments
Applicable to production bugs, test failures, performance issues, and integration problems, ensuring fixes target the root cause

Quick Start

Describe a debugging scenario and apply Phase 1 steps to gather evidence before proposing fixes.

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 workflow for finding software bug root causes?▼

Systematic debugging is a disciplined workflow that enforces evidence gathering and reproducibility to identify root causes before applying fixes. It eliminates guesswork by guiding teams through a structured four-phase analysis process.

How do I debug a production failure using a phased root cause analysis approach?▼

To debug a production failure, apply the four-phase root cause analysis workflow: investigate evidence, analyze patterns, test hypotheses, and implement fixes. This structured approach ensures reproducibility across environments before deployment.

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

Yes, this systematic debugging workflow applies to production bugs, test failures, performance issues, and integration problems across development pipelines. It guides teams through evidence gathering and hypothesis testing regardless of the issue type.

What is the best way to resolve test failures without guessing the root cause?▼

The best way to resolve test failures without guessing is following a phased workflow that enforces evidence gathering and pattern analysis before proposing fixes. This ensures the root cause is identified and verified through structured hypothesis testing.

Why does my software fix keep causing new bugs instead of resolving the original issue?▼

Your fixes likely address symptoms rather than root causes. Systematic debugging enforces a four-phase workflow with evidence gathering and traceability to ensure fixes target the actual root cause while maintaining quality gates.

When should I avoid quick fixes and apply a full root cause investigation workflow?▼

You should apply a full root cause investigation workflow when facing production bugs, test failures, or integration problems where reproducibility matters. Quick fixes risk recurring issues without the evidence gathering and phase-wise analysis this workflow provides.