systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: Silac

Enforce a four-phase workflow to identify root causes before fixes.

Updated Aug 27, 2026

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

Ready to run

npx skills add https://github.com/Silac1995/My-World-Isekai-Unity --skill systematic-debugging-silac1995

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/Silac1995/My-World-Isekai-Unity/tree/main/.claude/skills/systematic-debugging
Command: npx skills add https://github.com/Silac1995/My-World-Isekai-Unity --skill systematic-debugging-silac1995

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps engineers systematically identify and diagnose root causes before proposing fixes during debugging.

Core Features & Use Cases

Provides a four-phase framework (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to structure debugging.
Encourages defensive practices like defense-in-depth and trace-based reasoning to prevent symptom-driven fixes.
Supports learning and auditing with documented phases, rules, and testing guidance for repeated reliability.

Quick Start

Follow the four-phase process in order to identify 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?▼

To find the root cause of a bug, apply a four-phase debugging workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. This enforces trace-based reasoning to prevent symptom-focused fixes.

What is the best way to systematically debug flaky systems during production incidents?▼

Systematic debugging of flaky systems uses a structured four-phase process with defensive checks and defense-in-depth practices. This ensures you address the actual root cause of production incidents before applying any code changes.

How do I structure a debugging process for time-sensitive emergencies?▼

Structure debugging for time-sensitive emergencies by enforcing explicit phases: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. This prevents rushed symptom-focused fixes and ensures root causes are resolved.

Can I use a structured debugging process to audit and learn from past incidents?▼

Yes, you can audit and learn from past incidents using a documented four-phase debugging framework. It provides explicit rules, phases, and testing guidance to ensure repeated reliability and trace-based reasoning for future reference.

Why do my software fixes keep causing new issues in testing?▼

Software fixes cause new issues when they target symptoms instead of root causes. By applying defense-in-depth and a structured hypothesis testing phase, you can verify the exact root cause before making changes, preventing recurring failures.