skills.rest
AndrewChang-cpu
AndrewChang-cpuCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Investigate root causes before applying fixes in codebases and incidents.

Updated Mar 22, 2026
Search Tags:#testing#debugging#anti-patterns#systematic#tracing#phases#root-cause
One-click install
npx skills add https://github.com/AndrewChang-cpu/vibe-coding-configuration --skill systematic-debugging-andrewchang-cpu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/AndrewChang-cpu/vibe-coding-configuration/tree/main/general-plugin/skills/systematic-debugging
Command: npx skills add https://github.com/AndrewChang-cpu/vibe-coding-configuration --skill systematic-debugging-andrewchang-cpu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solves the problem of identifying root causes before applying fixes in any bug or failure.

Core Features & Use Cases

  • Phase-driven debugging: Phase 1 root cause investigation, Phase 2 pattern analysis, Phase 3 hypothesis/testing, Phase 4 implementation validation.
  • Anti-pattern awareness: explicit stop rules and "STOP and re-analyze" guidelines to resist shortcuts.
  • Defensive practice: supports tracing and defense-in-depth concepts for robust fixes in complex systems.

Quick Start

Follow the four-phase process starting with root cause investigation 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 the best way to find a root cause before applying fixes during production outages?▼

Systematic debugging uses a four-phase process of root cause investigation, pattern analysis, hypothesis testing, and implementation validation to find failure origins before applying fixes. It enforces explicit stop rules to prevent premature patches during complex incidents.

How do I systematically debug integration issues and test failures across a codebase?▼

Systematically debug integration issues and test failures by following a four-phase process: root cause investigation, pattern analysis, hypothesis testing, and implementation validation. This enforces tracing and defense-in-depth for robust fixes across codebases.

Why does my debugging process fail to prevent recurring incidents and integration issues?▼

Debugging fails to prevent recurring integration issues when anti-patterns bypass root cause investigation. Enforcing explicit stop rules and a four-phase process ensures you identify the true origin before applying fixes.

When do I need to stop analyzing and start implementing a fix during failure investigation?▼

You transition to implementation after completing root cause investigation, pattern analysis, and hypothesis testing. Explicit stop rules dictate when to stop analyzing and apply defense-in-depth fixes for complex system failures.

Related Skills

Explore More Software Engineering Skills→
miptah21miptah21
2

rca-diagnostics

Trace multi-system logs backward to isolate initiating causes of cascading failures.

Community
Advanced
lv7devlv7dev

debugging

Investigate root causes before implementing fixes through a four-phase debugging workflow.

Community
Advanced
aporto-techaporto-tech

Qa Only

Generate QA reports with health scores and screenshots for web applications.

Official
Advanced
ArabelaTsoArabelaTso
142

bug-to-patch-generator

Generate code patches from bug reports and failing tests.

Community
Advanced