guild-systematic-debug

Guide a four-phase debugging workflow to identify root causes of bugs and flaky tests.

6|Updated Apr 24, 2026

Search Tags:#qa #defense-in-depth #root-cause #systematic-debugging #root-cause-tracing #bug-triage #debugging-process

Ready to run

npx skills add https://github.com/lookatitude/guild --skill guild-systematic-debug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: guild-systematic-debug
Source: https://github.com/lookatitude/guild/tree/main/skills/fallback/systematic-debug
Command: npx skills add https://github.com/lookatitude/guild --skill guild-systematic-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging guides teams to identify root causes of bugs, flaky tests, and unexpected behavior before proposing fixes, replacing guesswork with a disciplined four-phase workflow and defense-in-depth practices.

Core Features & Use Cases

A structured four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
Supports root-cause tracing and defense-in-depth to catch issues across multiple layers and environments.
Integrates with related references and techniques (root-cause-tracing.md, defense-in-depth.md, condition-based-waiting.md) and related Guild skills (guild:tdd, guild:verify-done).

Quick Start

Begin with Phase 1 Root Cause Investigation to reproduce the issue, collect evidence, and trace data flow before formulating a fix.

Frequently Asked Questions about guild-systematic-debug

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

FAQPage Schema

How do I find the root cause of a flaky test or unexpected bug?▼

Root cause debugging requires a structured four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation, replacing guesswork with discipline. This approach traces issues deep in the stack before fixes are proposed.

What is the best way to debug complex software issues deep in the stack?▼

Systematic debugging applies defense-in-depth techniques to catch issues across multiple layers and environments. It guides teams through a repeatable analysis process to identify root causes and ensure safe, verified resolutions.

How do I start a systematic debugging process for bug triage?▼

Begin Phase 1 Root Cause Investigation to reproduce the issue, collect evidence, and trace data flow. This initial phase ensures you understand the problem thoroughly before formulating any fix.

Does systematic debugging work for analyzing unexpected behavior across different environments?▼

Yes, systematic debugging supports root-cause tracing and defense-in-depth to catch issues across multiple layers and environments. It provides a repeatable analysis process for complex software engineering scenarios.

Why should I use a structured debugging workflow instead of immediately proposing fixes?▼

A structured debugging workflow replaces guesswork with disciplined analysis, ensuring you identify root causes before implementation. This prevents recurring issues and provides defense-in-depth across your software stack.

When should I not use guesswork for bug triage and unexpected behavior?▼

You should avoid guesswork when issues are deep in the stack or require repeatable analysis. Systematic debugging ensures you trace data flow and test hypotheses before implementing fixes.