skills.rest
revan710517539
revan710517539COMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps engineers identify the root cause of bugs and prevent symptom-based fixes, reducing firefighting and rework.

Core Features & Use Cases

  • Four-phase workflow: Phase 1 Root Cause Investigation, Phase 2 Pattern Analysis, Phase 3 Hypothesis and Testing, Phase 4 Implementation.
  • Anti-pattern awareness and defense-in-depth guidance to prevent superficial fixes.
  • Real-world applicability across code failures, production incidents, flaky tests, and complex systems.

Quick Start

Begin with Phase 1 to collect evidence, then proceed through Phase 2 and Phase 3 before implementing Phase 4 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?▼

Root-cause debugging enforces a four-phase workflow: investigate root causes, analyze patterns, test hypotheses, and implement fixes. Completing Phase 1 evidence collection before patching prevents symptom-based fixes and recurring firefighting.

What is the best way to debug flaky tests in a complex multi-component system?▼

Debugging flaky tests in complex multi-component systems requires systematic data flow tracing. You investigate root causes, analyze failure patterns, test hypotheses, and implement fixes to prevent symptom-based patches and reduce rework.

How do I stop firefighting and prevent recurring production incidents?▼

To stop firefighting production incidents, apply defense-in-depth and anti-pattern awareness during root-cause investigation. Enforcing evidence collection before implementing fixes eliminates symptom-based patches that cause recurring incidents and rework.

Does systematic debugging work for tracing data flow across multiple components?▼

Yes, systematic debugging applies directly to complex, multi-component systems where tracing data flow is needed. It enforces a four-phase workflow spanning root cause investigation, pattern analysis, hypothesis testing, and implementation.

Why do my bug fixes keep causing new issues or requiring rework?▼

Your bug fixes cause rework because they are symptom-based rather than root-cause fixes. Applying a systematic debugging workflow with pattern analysis and hypothesis testing before implementation prevents superficial patches and recurring failures.

Related Skills

Explore More Software Engineering Skills→
PlazaCCPlazaCC
2

systematic-debugging

Enforce root-cause investigation before fixes in a four-phase debugging workflow.

Official
Advanced
Neroro64Neroro64

systematic-debugging

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

Community
Advanced
Avi977Avi977

systematic-debugging

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

Community
Advanced
doitiandoitian
14

systematic-debugging

Enforce a four-phase root-cause debugging process for code and tests.

Community
Advanced