systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: sjw2005

Locate root causes of bugs through four systematic debugging phases.

Updated Aug 27, 2026

Search Tags:#testing #debugging #validation #defense-in-depth #systematic #phases #root-cause

Ready to run

npx skills add https://github.com/Sjw2005/https---gitee.com-song-jiawei-2005-yolopro --skill systematic-debugging-sjw2005

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Sjw2005/https---gitee.com-song-jiawei-2005-yolopro/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/Sjw2005/https---gitee.com-song-jiawei-2005-yolopro --skill systematic-debugging-sjw2005

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging helps engineers avoid symptom fixes by enforcing root-cause analysis for bugs, test failures, and unexpected behavior.

Core Features & Use Cases

Phase-based approach with four mandatory phases: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation.
Anti-patterns and defenses to prevent rushing fixes and ensure traceability.
Works for debugging across small bugs to complex production outages and integrates with testing workflows.

Quick Start

Follow the four phases in order to systematically trace root causes before proposing 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 phase-based approach to locate the true origin of bugs before implementing fixes. It requires completing four mandatory phases: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation.

What is the best way to debug a complex production outage systematically?▼

Systematic debugging handles complex production outages by enforcing evidence gathering, traceability, and defense-in-depth validation. This prevents rushing shortcut fixes and ensures you trace the root cause through structured phases before applying a patch.

How do I stop applying shortcut fixes when resolving test failures?▼

You can stop applying shortcut fixes by following a systematic debugging process with explicit checks and anti-patterns. This methodology enforces pattern analysis and hypothesis testing to validate that your fix addresses the actual failure.

Can I integrate systematic debugging into my existing testing workflows?▼

Yes, systematic debugging integrates with testing workflows by requiring validation and hypothesis testing before implementation. This defense-in-depth approach ensures your test failure analysis maintains traceability and prevents superficial patches.

What are the limitations of using a phase-based approach for root cause analysis?▼

The limitation of this phase-based debugging approach is that it requires completing all four mandatory phases without skipping steps. This strict enforcement of evidence gathering and anti-pattern checks may slow down incident fixes that require immediate patching.