skills.rest
hxk622
hxk622COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Guide structured four-phase root cause analysis for software bugs and test failures.

8|Updated Jan 13, 2026
Search Tags:#debugging#investigation#bug fix#troubleshoot#debug#root-cause
One-click install
npx skills add https://github.com/hxk622/TokenDance --skill systematic-debugging-hxk622
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/hxk622/TokenDance/tree/main/backend/app/skills/builtin/superpowers/systematic-debugging
Command: npx skills add https://github.com/hxk622/TokenDance --skill systematic-debugging-hxk622

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill prevents wasted time and new bugs by ensuring you always find the root cause of an issue before attempting any fixes, especially under pressure.

Core Features & Use Cases

  • Systematic Investigation: Guides you through a 4-phase process (Investigation, Pattern Analysis, Hypothesis, Implementation) to uncover the true source of bugs.
  • Pressure Resistance: Provides explicit rules and anti-patterns to prevent shortcuts when time-constrained or facing obvious "quick fixes."
  • Use Case: When a critical production bug appears, load this skill to ensure a thorough root cause analysis, preventing symptom-fixing that leads to more problems.

Quick Start

Use the systematic-debugging skill to investigate any bug or test failure before proposing a 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 software bug instead of just fixing the symptom?▼

To find the root cause of a software bug, follow a structured four-phase process: systematic investigation, pattern analysis, hypothesis testing, and careful implementation. This prevents symptom-fixing and ensures robust solutions.

What is the best way to troubleshoot a critical production bug under time pressure?▼

The best way to troubleshoot a critical production bug under pressure is to use explicit rules and anti-patterns that resist shortcuts. This ensures thorough root cause analysis before attempting any fixes, preventing new bugs.

How do I systematically debug a failing test without guessing the fix?▼

Systematically debug a failing test by analyzing patterns and forming hypotheses based on investigation evidence. Testing these hypotheses prevents guessing and ensures you address the true source of the failure.

Why do my quick bug fixes keep introducing new problems in my code?▼

Quick bug fixes introduce new problems when they address symptoms rather than the root cause. Applying a structured debugging process prevents these rationalizations and ensures the underlying issue is fully resolved.

When should I use a structured debugging process for troubleshooting?▼

You should use a structured debugging process whenever you face any bug or test failure, especially critical production issues. It prevents wasted time and new bugs by ensuring thorough investigation before proposing a fix.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
bostonaholicbostonaholic
8

test-driven-bug-fix

Reproduce, isolate, fix, and verify software defects using test-driven methodology.

Community
Advanced
GeargrindadminGeargrindadmin

architecture

Analyze architectural trade-offs and document decisions with ADR templates.

Community
Intermediate
westnwestn
1

investigate

Identify root causes of software bugs through a structured four-phase debugging workflow.

Community
Advanced