skills.rest
LPDigital-Agent
LPDigital-AgentOFFICIAL
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Guide teams through four-phase systematic debugging to identify root causes before fixes.

Updated Aug 27, 2026
Search Tags:#testing#debugging#root cause#defense-in-depth#systematic#phases
One-click install
npx skills add https://github.com/LPDigital-Agent/galderma-demo-trackwise --skill systematic-debugging-lpdigital-agent
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/LPDigital-Agent/galderma-demo-trackwise/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/LPDigital-Agent/galderma-demo-trackwise --skill systematic-debugging-lpdigital-agent

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined, four-phase approach to diagnosing bugs, ensuring you reveal the root cause before proposing fixes and resist shortcuts under pressure.

Core Features & Use Cases

  • Four-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation.
  • Defensive design: Emphasizes never fixing symptoms, and incorporate defense-in-depth strategies.
  • Use cases: For production incidents, flaky tests, and complex systems where symptoms mask root causes.

Quick Start

  • Load the skill from skills/debugging/systematic-debugging.
  • Read the overview and begin Phase 1: Root Cause Investigation.
  • Complete Phase 1 before proposing fixes, then proceed through Phase 2–4 to ensure a root-cause-based resolution.

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 proposing a fix?▼

To find a bug's root cause before fixing, apply a systematic debugging process enforcing a complete Root Cause Investigation phase before any implementation, preventing you from merely treating symptoms.

What is the best way to debug production incidents under time pressure?▼

The best way to debug production incidents under time pressure is a four-phase systematic approach: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, then Implementation, which resists shortcuts.

How do I stop fixing symptoms instead of the actual root cause during debugging?▼

To stop fixing symptoms during debugging, enforce a phased process requiring Root Cause Investigation and Pattern Analysis completion before entering Hypothesis and Testing or Implementation phases.

Does systematic debugging work for flaky test failures and performance issues?▼

Yes, systematic debugging works for flaky test failures and performance issues. The four-phase method applies to complex systems where symptoms mask root causes, ensuring thorough Pattern Analysis and Hypothesis Testing.

When should I not use a trial-and-error approach to fix integration problems?▼

Avoid trial-and-error for integration problems when symptoms mask root causes or under time pressure. Use systematic debugging to enforce Hypothesis and Testing and incorporate defense-in-depth strategies before Implementation.

Related Skills

Explore More Software Engineering Skills→
mwathibenmwathiben

systematic-debugging

Diagnose bugs and production issues using a four-phase systematic workflow.

Community
Advanced
FerranGuardiaFerranGuardia

systematic-debugging

Identify root causes before implementing fixes across software bugs and incidents.

Community
Advanced
HouseofmvpsHouseofmvps
115

systematic-debugging

Investigate root causes through a 4-phase structured debugging workflow.

Community
Advanced
romiluz13romiluz13
161

debugging-patterns

Enforce root-cause investigation before applying fixes in debugging workflows.

Community
Advanced