systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: ahmedelhadarey

Guide teams through a four-phase root-cause investigation workflow.

2|Updated Feb 25, 2026

Search Tags:#testing #debugging #investigation #defense-in-depth #systematic #phases #root-cause

Ready to run

npx skills add https://github.com/AhmedElhadarey/Gilfoyle --skill systematic-debugging-ahmedelhadarey

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a structured approach to uncover root causes, eliminating symptomatic fixes and guiding teams to fix the source.

Core Features & Use Cases

Four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation.
Anti-patterns and defense-in-depth recommendations to prevent regression.
Reference materials like root-cause tracing and stack-trace instrumentation to aid diagnosis.
Use cases include production bugs, test failures, and unexpected behavior in complex systems.

Quick Start

Run through Phase 1 to begin root-cause investigation and complete Phases 2–4 for a full fix.

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 production bug instead of just fixing the symptom?▼

Root-cause debugging replaces symptom fixes by guiding teams through a structured four-phase investigation: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. You collect explicit evidence to identify and fix the actual source of the issue.

What is the best way to debug test failures in complex systems?▼

Debugging test failures in complex systems requires a systematic investigation workflow that enforces evidence collection and pattern analysis before implementation. This approach traces unexpected behavior back to its origin rather than applying patches.

How do I prevent bug regression after a root-cause fix?▼

To prevent regression, systematic debugging integrates defense-in-depth validation during the implementation phase. It provides anti-pattern recommendations and validates integration points to ensure the root-cause fix holds under future system stress.

Can I skip the initial investigation phase if I already have a hypothesis for the bug?▼

No, Phase 1 Root Cause Investigation is non-skippable. The workflow requires explicit evidence collection and defined success criteria before moving to hypothesis testing, ensuring your assumptions are validated against actual system data.

Does systematic debugging work for unexpected behavior in development environments?▼

Yes, systematic debugging handles both production and development bugs, including unexpected behavior in complex systems. It uses root-cause tracing and stack-trace instrumentation reference materials to aid diagnosis across environments.

What tools do I need for root-cause tracing and stack-trace instrumentation?▼

The workflow supports optional tools and reference materials for root-cause tracing and stack-trace instrumentation. You need to provide explicit evidence collection inputs and define success criteria to complete the investigation phases effectively.