skills.rest
lightxue
lightxueCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Identify and fix root causes using a four-phase debugging workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers reliably identify and fix root causes of bugs and failures by following a disciplined, four-phase debugging process.

Core Features & Use Cases

  • Four-phase framework (Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, Implementation) to systematically uncover root causes.
  • Anti-patterns, defense-in-depth guidance, and stack-trace oriented diagnostics to resist time pressure and avoid symptom fixes.
  • Practical playbooks and references (root-cause-tracing, defense-in-depth, condition-based waiting) to strengthen debugging across teams.

Quick Start

Load the Systematic Debugging skill and complete Phase 1 before proposing any fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema
What is systematic debugging and how does it help find root causes of bugs?▼

Systematic debugging is a structured, four-phase process—root cause investigation, pattern analysis, hypothesis testing, and implementation—that reliably uncovers and fixes the true root causes of bugs instead of just treating symptoms.

How do I debug production issues and test failures without applying symptom fixes?▼

Debug production issues and test failures by following a disciplined workflow that enforces stack-trace oriented diagnostics, pattern analysis, and hypothesis testing before implementation, resisting time pressure to ensure durable, verifiable fixes.

When should I use a structured debugging process for software failures and performance quirks?▼

Use a structured debugging process when facing complex software failures, performance quirks, or integration problems where time pressure might push you toward symptom fixes, ensuring you verify root causes through defense-in-depth checks.

Can I apply this debugging workflow to integration problems across different software systems?▼

Yes, this debugging workflow applies to integration problems across software systems, using pattern analysis and condition-based waiting playbooks to systematically trace failures and implement verifiable, durable fixes.

What's the best way to stop recurring bugs and prevent symptom fixes in my codebase?▼

The best way to stop recurring bugs is to enforce anti-patterns and defense-in-depth guidance during implementation, ensuring every fix passes through root-cause investigation and hypothesis testing to verify the source of the failure.

Related Skills

Explore More Software Engineering Skills→
devs6186devs6186

gstack-openclaw-investigate

Diagnose software bugs through a phase-driven debugging workflow and produce debug reports.

Community
Advanced
dmulcaheydmulcahey

systematic-debugging

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

Community
Advanced
htlin222htlin222
77

error-detective

Search and analyze log files and codebases for error patterns and stack traces.

Community
Intermediate
jcl2018jcl2018

CJ_goal_task

Convert small ad-hoc tasks into pull requests via bash scripting.

Community
Intermediate