skills.rest
gquthier
gquthierCOMMUNITY
Explore all skills by this author →
Website𝕏@gauthierthiryGitHub

systematic-debugging

Identifies root causes of bugs through a four-phase diagnostic process.

14|2|Updated Mar 29, 2026
Search Tags:#testing#debugging#instrumentation#reproduce#root-cause#data-flow
One-click install
npx skills add https://github.com/gquthier/CLAWG --skill systematic-debugging-gquthier
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/gquthier/CLAWG/tree/main/skills/software-development/systematic-debugging
Command: npx skills add https://github.com/gquthier/CLAWG --skill systematic-debugging-gquthier

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and mask underlying issues. This Phase-driven approach ensures you identify the root cause before attempting any fix.

Core Features & Use Cases

  • Phase-driven debugging: four phases (Root Cause Investigation, Pattern Analysis, Hypothesis Testing, Implementation) to structure your debugging process.
  • Reproducibility and evidence: emphasizes reproducibility, logging, and data-flow tracing to pinpoint issues.
  • Multi-component resilience: applicable to issues across API → service → database boundaries and cross-cutting concerns.
  • Guardrails and test-first recovery: encourages validation and test-driven steps to prevent regressions.

Quick Start

Begin Phase 1 by reading error messages, reproducing the issue, and gathering evidence to identify the root cause.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
How do I identify the root cause of a bug before attempting a fix?▼

Root cause debugging involves reproducing the issue, analyzing error logs, and tracing data-flow across components to pinpoint the underlying fault before applying any corrective code changes.

What is the best way to debug production bugs across API and database boundaries?▼

Multi-component debugging requires log-guided diagnostics and data-flow tracing across API, service, and database boundaries to systematically reproduce the issue and confirm the exact failure point.

How do I systematically debug test failures and unexpected application behavior?▼

Systematic debugging structures the process into four phases: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation, ensuring you validate evidence before modifying code.

Why do random fixes waste time and mask underlying software issues?▼

Random fixes mask underlying issues because they address symptoms without evidence. A disciplined debugging approach uses reproducibility and hypothesis testing to ensure the actual root cause is resolved.

Can I use a phase-driven debugging approach for performance and integration problems?▼

Yes, phase-driven debugging is applicable to performance issues and integration problems by gathering evidence, testing hypotheses against data-flow patterns, and implementing test-first recovery steps to prevent regressions.

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
enigmaicon-engenigmaicon-eng
1

test-driven-development

Implement a test-first workflow with failing tests and minimal production code.

Community
Advanced
Im5tuIm5tu
6

systematic-debugging

Identify root causes of software bugs through a four-phase debugging process.

Community
Advanced
amanikamanik

investigate

Trace error symptoms to underlying causes using a structured four-phase debugging workflow.

Community
Advanced