systematic-debugging

Guide a four-phase debugging workflow for reproduction, isolation, root cause, and fix verification.

Updated Aug 27, 2026

Search Tags:#debugging #checklist #isolation #verification #reproduce #root-cause-analysis #incident-response

Ready to run

npx skills add https://github.com/JoaoPedroAmaral/backBarbearia --skill systematic-debugging-joaopedroamaral

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/JoaoPedroAmaral/backBarbearia/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/JoaoPedroAmaral/backBarbearia --skill systematic-debugging-joaopedroamaral

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a repeatable, evidence-driven approach to diagnosing and resolving complex software bugs so teams avoid guesswork and regressions.

Core Features & Use Cases

4-phase workflow: Reproduce, Isolate, Understand (root cause), and Fix & Verify with clear checkpoints.
Root cause techniques: Guided 5-Whys analysis, minimal reproducible cases, and isolation questions to narrow scope.
Verification & prevention: Fix verification checklist and regression test guidance to ensure durable resolutions.
Use Case: When an intermittent production error lacks clear origin, apply this methodology to build a minimal repro, identify the root cause, and verify the fix across environments.

Quick Start

Use the systematic-debugging methodology to reproduce the issue reliably, isolate the smallest failing case, perform root cause analysis with the 5 Whys, and verify the fix with tests and log-based evidence.

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

A systematic debugging workflow provides a repeatable, evidence-driven approach to diagnose and resolve complex software bugs. It uses a 4-phase methodology: Reproduce, Isolate, Understand, and Fix & Verify, ensuring teams avoid guesswork and prevent regressions.

How do I find the root cause of an intermittent production error?▼

To find the root cause of an intermittent production error, apply guided 5-Whys analysis and build a minimal reproducible case. This methodology helps you isolate the smallest failing case and identify the origin across environments and codebases.

How do I isolate a bug to prevent regressions when fixing software?▼

To isolate a bug and prevent regressions, use systematic isolation questions to narrow scope, apply fix verification checklists, and follow regression test guidance. This ensures durable resolutions through evidence-based verification across environments.

What is the best way to verify a software fix across multiple environments?▼

The best way to verify a software fix across multiple environments is using a fix verification checklist with tests and log-based evidence. This structured approach confirms the resolution is durable and prevents future regressions in production.

Can I use this debugging methodology for any codebase and environment?▼

Yes, you can use this debugging methodology across environments and codebases. It is designed for reliable reproduction, root cause analysis, and systematic isolation, making it suitable for complex software issues regardless of the specific platform.