systematic-debugging

Enforce a four-phase root-cause debugging process before applying fixes.

Updated Apr 3, 2026

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

Ready to run

npx skills add https://github.com/handsomelong922/my-codex-skills --skill systematic-debugging-handsomelong922

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging enforces a four-phase, root-cause-first workflow, ensuring bugs are understood and fixed rather than patched superficially.

Core Features & Use Cases

Phase-driven investigation, pattern analysis, hypothesis testing, and implementation
Built-in guardrails to prevent skipping steps and to encourage thorough validation
Applicable to code defects, test failures, production incidents, and flaky behavior

Quick Start

Start by identifying the failing behavior, then apply the four phases to discover and address the root cause.

Frequently Asked Questions about systematic-debugging

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What is a systematic root-cause debugging process?▼

A systematic root-cause debugging process enforces a four-phase workflow—investigation, pattern analysis, hypothesis testing, and implementation—to ensure code defects are fully understood and permanently fixed rather than superficially patched.

How do I fix flaky behavior and test failures without introducing regressions?▼

Fix flaky behavior and test failures by applying a structured four-phase debugging process with built-in guardrails, defense-in-depth checks, and practical testing templates to validate hypotheses and significantly reduce regression risk.

When should I use a phase-driven debugging workflow for production incidents?▼

Use a phase-driven debugging workflow for production incidents when you need to identify root causes before applying fixes, ensuring robust and long-lasting resolutions for code defects, test failures, and complex flaky behavior.

What's the best way to investigate a bug before writing a fix?▼

The best way to investigate a bug before writing a fix is to follow a structured root-cause investigation phase, analyzing patterns and testing hypotheses systematically to guarantee the implementation addresses the actual defect.

How do debugging guardrails prevent skipping steps during hypothesis testing?▼

Debugging guardrails prevent skipping steps during hypothesis testing by enforcing a rigid four-phase sequence, requiring thorough validation and pattern analysis before moving to the implementation phase to ensure a robust resolution.

Does systematic debugging work for both code defects and production incidents?▼

Yes, systematic debugging works for both code defects and production incidents, applying its four-phase root-cause investigation, pattern analysis, hypothesis testing, and implementation process to achieve long-lasting resolutions across various failure types.