skills.rest
gong-type
gong-typeCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Trace bugs to root causes using a four-phase workflow with explicit gating.

Updated Aug 27, 2026
Search Tags:#debugging#defense-in-depth#root-cause#phase-management#root-cause-tracing
One-click install
npx skills add https://github.com/gong-type/skills --skill systematic-debugging-gong-type
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/gong-type/skills/tree/main/systematic-debugging
Command: npx skills add https://github.com/gong-type/skills --skill systematic-debugging-gong-type

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Trace bugs to their root cause before proposing fixes, preventing symptom-focused patches.

Core Features & Use Cases

  • Four-phase structured workflow (Root Cause Investigation → Pattern Analysis → Hypothesis & Testing → Implementation)
  • Anti-patterns guidance to resist time pressure and rushed decisions
  • Techniques for root-cause tracing and defensive validation across layers

Quick Start

Start by loading the skill and completing Phase 1 before attempting any 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 instead of just applying a quick fix?▼

To find a bug's root cause, you must trace it before proposing fixes, preventing symptom-focused patches. A structured workflow enforces root-cause investigation and pattern analysis to ensure robust, safe solutions.

What is the best way to debug flaky tests and production incidents?▼

Debugging flaky tests and production incidents requires a four-phase workflow: root cause investigation, pattern analysis, hypothesis testing, and implementation. This enforces explicit gating and defense-in-depth to resist rushed decisions.

How do I stop developers from rushing code fixes under time pressure?▼

To stop rushed code fixes, apply anti-pattern guidance that resists time pressure. Enforcing explicit gating between debugging phases ensures developers validate hypotheses and trace root causes before implementation.

When should I use defense-in-depth practices for code failures?▼

Use defense-in-depth practices for code failures when you need defensive validation across layers. This approach ensures you identify root causes and apply robust fixes rather than superficial patches.

What are the steps to trace a bug to its root cause?▼

Tracing a bug to its root cause involves four structured phases: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. You must complete Phase 1 before attempting any fixes.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
brainbrewlabsbrainbrewlabs
7

systematic-debugging

Diagnose software bug root causes through a four-phase investigation workflow.

Official
Advanced
InfinityBowmanInfinityBowman
3

Observability Analysis

Audit production observability stacks for logging, tracing, metrics, alerting, and debuggability.

Community
Advanced
timequitytimequity
6

systematic-debugging

Enforce a four-phase root-cause investigation workflow before applying fixes to bugs and test failures.

Official
Advanced