skills.rest
ytqh
ytqhCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Diagnose root causes through a four-phase evidence-driven debugging workflow.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides a disciplined, phase-based framework to diagnose bugs, failures, or unexpected behavior without resorting to symptom fixes, ensuring root causes are found and addressed.

Core Features & Use Cases

  • Structured 4-phase process: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation, with mandatory progression through each phase.
  • Anti-patterns and defenses: explicit guidance to resist time-pressure shortcuts and to stop and re-analyze when stuck.
  • Accessibility of references: built-in links and reference materials for tracing root causes and applying defense-in-depth strategies in real projects.
  • Use Case: When a bug arises in production, follow the skill to trace the source, validate across layers, and implement a robust fix.

Quick Start

  1. Open skills/debugging/systematic-debugging and read the overview.
  2. Follow Phase 1, Phase 2, Phase 3, and then Phase 4 in order.
  3. Consult the anti-patterns and references to avoid shortcuts and ensure a proper root-cause fix.

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 production failure instead of just fixing the symptom?▼

Root-cause debugging enforces a four-phase, evidence-driven workflow to trace data and control flow, ensuring you diagnose production failures and address the actual source rather than applying symptom fixes.

What is the best way to systematically debug performance regressions and integration problems?▼

Systematic debugging provides a repeatable method to trace performance regressions and integration problems through structured phases: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.

How do I stop taking debugging shortcuts when under time pressure to fix a bug?▼

To stop taking shortcuts under time pressure, this systematic debugging framework includes explicit anti-pattern defenses that guide you to stop, re-analyze when stuck, and validate across architectural layers.

Can I apply a structured debugging workflow to both test failures and unexpected software behavior?▼

Yes, this structured debugging workflow applies across software issues including test failures, unexpected behavior, and performance regressions, providing a disciplined phase-based framework to diagnose bugs reliably.

What are the limitations of using a phase-based debugging framework for urgent software issues?▼

The main limitation of phase-based debugging is the requirement for mandatory progression through all four phases, which enforces thorough evidence validation but may slow down urgent software issue resolution compared to symptom fixes.

Does defense-in-depth debugging require specific tools to trace data and control flow?▼

Defense-in-depth debugging relies on built-in reference materials and explicit instructions to trace data and control flow across layers, requiring no specific external dependencies to validate hypotheses and implement robust 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
hitsumabushi334hitsumabushi334

systematic-debugging

Guide engineers through a four-phase root cause debugging process.

Community
Advanced
mwaymway
4

systematic-debugging

Identify root causes of bugs and test failures through a four-phase debugging workflow.

Community
Advanced
NintendaDevNintendaDev
16

unikit-fix

Automate end-to-end bug-fix workflows in UniKit AI projects.

Community
Advanced