systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: fred29910

Identify root causes of bugs through a four-phase evidence-driven debugging workflow.

Updated May 4, 2026

Search Tags:#debugging #investigation #anti-patterns #root-cause #phased-workflow #evidence-tracing #production-resilience

Ready to run

npx skills add https://github.com/fred29910/migra-go --skill systematic-debugging-fred29910

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/fred29910/migra-go/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/fred29910/migra-go --skill systematic-debugging-fred29910

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents rash, symptom-focused fixes by enforcing a disciplined, four-phase approach to debugging that prioritizes root-cause analysis before any repair.

Core Features & Use Cases

Phase-based workflow: first investigate root cause, then analyze patterns, form and test hypotheses, and implement fixes with safeguards.
Anti-pattern defenses: explicit guidance to avoid shortcuts like knee-jerk patches, rushing under pressure, and speculative fixes.
Evidence-driven validation: promotes tracing data flow, logging, and multi-layer checks to ensure robust repairs.

Quick Start

Follow the four-phase process to perform root-cause debugging before proposing fixes.

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 bug before applying a fix?▼

To find a root cause before fixing a bug, follow an evidence-driven, four-phase workflow that prioritizes investigation, pattern analysis, hypothesis testing, and staged verification over symptom-focused patches.

What is the best way to debug production incidents without causing regressions?▼

The best way to debug production incidents without regressions is using a phased workflow that requires documented error analysis, reproducible steps, evidence tracing, and staged verification to ensure repairs address root causes.

How do I stop speculative fixes when debugging failing tests?▼

To stop speculative fixes when debugging failing tests, apply anti-pattern defenses that explicitly guide you away from knee-jerk patches, rushing under pressure, and shortcuts, enforcing documented evidence tracing first.

Can I use a phased debugging workflow for both test failures and production incidents?▼

Yes, a phased debugging workflow applies to both test failures and production incidents, guiding teams through root-cause investigation, pattern analysis, hypothesis testing, and fix implementation with multi-layer safeguards.

When should I not use symptom-focused patches during software debugging?▼

You should not use symptom-focused patches when rushing under pressure or facing complex failures; instead, use evidence-driven validation, trace data flow, and perform multi-layer checks to ensure robust repairs.

What steps are involved in an evidence-driven debugging workflow?▼

An evidence-driven debugging workflow involves four steps: investigate root causes, analyze patterns, form and test hypotheses, and implement fixes with safeguards, requiring documented error analysis and reproducible steps.