skills.rest
thimslugga
thimsluggaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

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

Updated Nov 29, 2025
Search Tags:#debugging#defense-in-depth#evidence#process#phases#root-cause
One-click install
npx skills add https://github.com/thimslugga/agent-skills --skill systematic-debugging-thimslugga
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/thimslugga/agent-skills/tree/main/skills/development/systematic-debugging
Command: npx skills add https://github.com/thimslugga/agent-skills --skill systematic-debugging-thimslugga

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined framework to identify root causes before proposing fixes, reducing wasted effort and repeated failures.

Core Features & Use Cases

  • Four-phase process (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to guide debugging.
  • Anti-patterns and defense-in-depth practices that deter shortcut fixes and promote evidence-based decisions.
  • Use cases include diagnosing production incidents, flaky tests, and complex multi-component systems.

Quick Start

Follow Phase 1 Root Cause Investigation before attempting any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is a systematic debugging process for finding root causes?▼

A systematic debugging process forces strict adherence to a four-phase, evidence-driven workflow to identify root causes before proposing fixes, reducing wasted effort and repeated failures.

How do I debug a production incident under time pressure?▼

To debug a production incident under time pressure, follow a phased root cause investigation framework that prioritizes thorough data collection and evidence-based decisions over shortcut fixes.

What are common debugging anti-patterns that cause repeated failures?▼

Common debugging anti-patterns involve skipping evidence collection and attempting shortcut fixes before identifying root causes, which a defense-in-depth strategy explicitly deters to ensure deterministic resolution.

How do I diagnose flaky tests in a complex multi-component system?▼

Diagnose flaky tests in complex multi-component systems by applying pattern analysis and hypothesis testing during a structured root cause investigation, ensuring all data is collected before implementing fixes.

When should I use a four-phase debugging workflow instead of quick fixes?▼

Use a four-phase debugging workflow instead of quick fixes when diagnosing complex multi-component failures or production incidents, where strict evidence-driven phases prevent wasted effort and repeated failures.

Related Skills

Explore More Software Engineering Skills→
gajjalaashok75-UIgajjalaashok75-UI
2

error-detective

Extract error patterns from logs and stack traces to identify root causes.

Community
Advanced
dmulcaheydmulcahey

systematic-debugging

Trace software bugs to root causes using a four-phase investigation methodology.

Community
Advanced
tclemtclem
11

investigate-alert

Diagnose production alerts by aggregating logs, metrics, traces, and source code.

Community
Advanced
alexandervashurinalexandervashurin

investigate

Guide structured four-phase debugging to isolate root causes in software systems.

Community
Advanced