systematic-debugging

Diagnose software defects through a four-phase root cause analysis workflow.

Updated Mar 23, 2026

Search Tags:#debugging #troubleshooting #root cause analysis #bug fixing #regression testing #reproduction #5 whys

Ready to run

npx skills add https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026 --skill systematic-debugging-helcio-nogueira

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/Helcio-Nogueira/Painel_Inteligente_Hackaton_2026 --skill systematic-debugging-helcio-nogueira

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Debugging often devolves into random guessing and symptom-patching that wastes time and leaves root causes unfixed. This Skill enforces a disciplined, evidence-based methodology so bugs are reproduced, isolated, understood, and verified before any fix is applied. ## Core Features & Use Cases - 4-Phase Process: Structured phases for Reproduce, Isolate, Understand (5 Whys root cause analysis), and Fix & Verify, each with ready-to-use Markdown templates. - Debugging Checklists: Before/during/after checklists covering reproduction consistency, log inspection, regression tests, and related code review. - Anti-Pattern Guardrails: Explicit warnings against random changes, ignoring evidence, and fixing without reproduction. - Use Case: A developer facing an intermittent production error uses the Reproduce phase to establish a reliable trigger, the 5 Whys to trace it to a race condition, and the verification checklist to confirm the fix with a regression test. ## Quick Start Ask the AI to debug a failing feature using the systematic debugging methodology, starting by reproducing the issue and documenting the root cause before proposing a fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I debug a complex bug systematically?▼

Follow a four-phase process: first reproduce the issue reliably and record the reproduction rate, then isolate the source by checking recent changes and minimal cases, find the root cause with the 5 Whys technique, and finally fix and verify with a regression test.

What is root cause analysis in debugging?▼

Root cause analysis identifies the underlying reason a bug occurs rather than its surface symptoms. The 5 Whys technique asks "why" iteratively—typically five times—to move from the first observation down to the true originating cause.

How do I reproduce an intermittent bug?▼

Document exact reproduction steps and classify the reproduction rate as always, often, sometimes, or rare. Check recent git changes, compare environments, and reduce the failing scenario to the smallest code change that still triggers the issue.

What are common debugging anti-patterns to avoid?▼

Avoid making random changes hoping something works, ignoring contradictory evidence, assuming a cause without proof, fixing before reproducing the issue, and stopping at symptoms instead of finding the root cause.

How do I verify a bug fix is complete?▼

Confirm the bug no longer reproduces, check that related functionality still works, ensure no new issues were introduced, and add a regression test. Also document the root cause and inspect similar code for the same defect.