systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: yangshu2087

Identify and isolate root causes of bugs before applying fixes.

Updated Mar 24, 2026

Search Tags:#debugging #defense-in-depth #systematic #traceability #root-cause #phase-based

Ready to run

npx skills add https://github.com/yangshu2087/Codex --skill systematic-debugging-yangshu2087

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/yangshu2087/Codex/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/yangshu2087/Codex --skill systematic-debugging-yangshu2087

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and create new bugs. Systematic debugging ensures root cause analysis before proposing fixes, reducing rework and surfacing underlying issues.

Core Features & Use Cases

Enforces a four-phase debugging workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation.
Includes guidance on tracing data flow, adding defense-in-depth validations, and using stack traces/instrumentation to diagnose issues.
Applicable across test failures, production bugs, and unexpected behavior in multi-component systems with detailed steps and best practices.

Quick Start

Begin with Phase 1: Root Cause Investigation to identify the original trigger.

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 bugs propagating across multiple components?▼

To find the root cause of bugs in multi-component systems, start with a root cause investigation phase to identify the original trigger, gather evidence, and trace data flow before applying fixes.

What is the best way to debug test failures in a CI environment?▼

The best way to debug test failures in CI environments is applying a systematic four-phase workflow: root cause investigation, pattern analysis, hypothesis testing, and implementation, guided by stack traces and instrumentation.

How do I stop random fixes from creating new bugs during debugging?▼

To stop random fixes from creating new bugs, enforce root cause analysis before proposing fixes, utilizing pattern analysis and controlled testing to surface underlying issues and reduce rework.

Why does adding defense-in-depth validations help with unexpected behavior?▼

Adding defense-in-depth validations helps with unexpected behavior by adding traceability through stack traces and instrumentation, isolating issues across system layers before they propagate further.

Can I use systematic debugging for production bugs and test failures?▼

Yes, you can use systematic debugging for production bugs, test failures, and unexpected behavior across multi-component systems, applying controlled testing and pattern analysis in both development and CI environments.