skills.rest
xhyqaq
xhyqaqCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Enforce a 4-phase root cause investigation process for software debugging.

63|2|Updated Mar 29, 2026
Search Tags:#workflow#debugging#root cause#bug fix#defense-in-depth#hypothesis testing#test failure
One-click install
npx skills add https://github.com/xhyqaq/superpowers-plus --skill systematic-debugging-xhyqaq
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/xhyqaq/superpowers-plus/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/xhyqaq/superpowers-plus --skill systematic-debugging-xhyqaq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random bug fixes waste hours, create new issues, and mask underlying root causes, especially under time pressure or when quick symptom patches seem obvious.

Core Features & Use Cases

  • 4-Phase Systematic Workflow: Structured process covering root cause investigation, pattern analysis, hypothesis testing, and implementation to ensure fixes address actual issues.
  • Pressure-Resistant Guardrails: Explicit rules, anti-pattern guidance, and mandatory checkpoints to resist shortcuts like symptom fixes or shotgun debugging when under time pressure.
  • Supporting Techniques: Includes root cause tracing, defense-in-depth validation, and condition-based waiting to address common debugging pitfalls like flaky tests and deep call stack issues.
  • Use Case: Ideal for any test failure, production bug, unexpected behavior, or performance issue, especially when previous fixes have failed or you don't fully understand the problem.

Quick Start

When you encounter any bug, test failure, or unexpected behavior, use the systematic-debugging skill to follow its 4-phase process and identify the root cause before attempting any fixes.

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

To find the root cause of a bug reliably, you must enforce a structured 4-phase systematic debugging workflow covering root cause investigation, pattern analysis, hypothesis testing, and implementation. This prevents random symptom patches and guesswork.

What is the best way to debug recurring test failures under time pressure?▼

The best way to debug recurring test failures under time pressure is using pressure-resistant guardrails with explicit rules and mandatory checkpoints. This enforces hypothesis testing and prevents shotgun debugging shortcuts when fixing unexpected behavior.

How do I stop recurring bugs and wasted time from random fixes in production?▼

To stop recurring bugs from random fixes in production, apply backward data flow tracing and defense-in-depth validation during your root cause investigation. This structured process ensures your bug fix addresses the actual underlying issue.

Why do my previous bug fixes fail to resolve unexpected behavior in my software?▼

Previous bug fixes fail to resolve unexpected behavior when they mask underlying root causes with quick symptom patches. A systematic debugging process with anti-pattern detection and hypothesis testing is required to identify the true issue.

How do I debug flaky tests and deep call stack issues systematically?▼

To debug flaky tests and deep call stack issues systematically, apply supporting techniques like condition-based waiting and backward data flow tracing. These methods address common debugging pitfalls within the structured 4-phase workflow.

Does systematic debugging work for build failures and integration errors?▼

Yes, systematic debugging works for build failures and integration errors. The 4-phase root cause investigation process applies to all technical debugging scenarios including performance issues, test failures, and production bugs.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
maxjuniorbrmaxjuniorbr
2

systematic-debugging

Guide root-cause debugging through a four-phase investigation workflow.

Community
Advanced
a-ariffa-ariff
14

root-cause-tracing

Trace bugs backward from symptoms to identify root causes.

Community
Intermediate
kk20300113-pngkk20300113-png

investigate

Guide structured root-cause debugging for software errors and regressions.

Community
Advanced