systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: oalansilva

Identify and fix software bugs through a 4-phase debugging workflow.

Updated Dec 28, 2025

Search Tags:#debugging #verification #checklists #root-cause-analysis #5-whys #reproducible-steps #isolation-questions

Ready to run

npx skills add https://github.com/oalansilva/crypto --skill systematic-debugging-oalansilva

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This capability provides a structured debugging framework to prevent guesswork and ensure root-cause clarity before implementing fixes.

Core Features & Use Cases

4-Phase Debugging: Reproduce, Isolate, Understand, and Fix & Verify to systematically approach issues.
Reproduction & Isolation: Guides to collect exact steps, determine environmental impact, and minimize changes for reliable diagnosis.
Root Cause Analysis: Incorporates the 5 Whys technique and explicit questions to reveal the underlying cause.
Verification & Checks: Provides a clear fix verification checklist to prevent regressions and document findings.

Quick Start

Outline reproducible steps, answer isolation questions, perform a root-cause analysis, and verify the fix with documentation.

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 complex software bug?▼

A structured debugging workflow finds root causes by guiding you through four phases: Reproduce, Isolate, Understand, and Fix & Verify. It enforces deterministic reproduction steps, isolation questions, and the 5 Whys technique to reveal underlying causes before implementing fixes.

What is the best way to debug production incidents systematically?▼

The best way to debug production incidents systematically is a 4-phase workflow that collects exact reproduction steps, determines environmental impact, minimizes changes for diagnosis, and uses a verification checklist to prevent regressions.

How does the 5 Whys technique work for root-cause analysis?▼

The 5 Whys technique works for root-cause analysis by prompting you to ask explicit isolation questions repeatedly. This structured framework reveals the underlying cause of software bugs rather than treating surface symptoms.

Can I use this structured debugging workflow for software development and production environments?▼

Yes, this structured debugging workflow is applicable to both software development and production incidents. It guides engineers through reproduction and isolation to determine environmental impacts and ensure reliable diagnosis across diverse environments.

How do I verify a software fix and prevent regressions after debugging?▼

You verify a software fix and prevent regressions by applying a clear verification checklist. This structured debugging phase ensures deterministic reproduction, documents findings, and confirms the root cause is resolved without introducing new issues.