systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: zhanglongxiao111

Investigate root causes through four phases before proposing debugging fixes.

35|5|Updated Sep 20, 2025

Search Tags:#debugging #anti-patterns #root cause #test failures #hypothesis testing #architecture review

Ready to run

npx skills add https://github.com/zhanglongxiao111/indesign-cli --skill systematic-debugging-zhanglongxiao111

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic debugging prevents wasted time and new regressions by requiring root-cause investigation before proposing any fixes, even under pressure.

Core Features & Use Cases

Four-phase, pressure-resistant workflow: Investigation → Pattern Analysis → Hypothesis/Testing → Implementation, with explicit “must not skip” rules.
Failure-aware decision making: If a first hypothesis fails, the skill requires forming a new hypothesis rather than stacking additional fixes.
Guardrails against rationalizations: Clear red flags for stopping, re-analyzing, and questioning architecture after 3+ failed fixes.

Quick Start

Ask your AI to follow Phase 1: Root Cause Investigation by reading the error messages carefully, reproducing the issue consistently, and tracing the failing data back to its original trigger before suggesting any fix.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is systematic debugging and when do I need root cause investigation?▼

Systematic debugging requires root cause investigation before proposing fixes. You need it for bugs, test failures, performance issues, and build failures where you might otherwise guess fixes and cause regressions.

How do I debug test failures without guessing fixes?▼

Debug test failures by following a four-phase workflow: investigation, pattern analysis, hypothesis testing, and implementation. Form a single hypothesis, test it with minimal changes, and verify before applying any fix.

What should I do when my debugging fixes keep failing?▼

When debugging fixes fail, stop stacking patches. If a hypothesis fails, form a new one. After three failed fixes, trigger the escalation rule to re-analyze the issue or question the architecture.

How do I find the root cause of unexpected application behavior?▼

Find the root cause of unexpected behavior by reading error messages, reproducing the issue consistently, and tracing failing data back to its original trigger during the investigation phase before suggesting changes.

Does systematic debugging work for build failures and integration problems?▼

Yes, systematic debugging applies to build failures and integration problems. It directs root-cause investigation across all failure types, preventing wasted time and new regressions under pressure.

What are the limitations of guessing fixes during debugging?▼

Guessing fixes during debugging wastes time and introduces regressions. Systematic debugging enforces mandatory verification and single-hypothesis testing to prevent rationalizations and ensure the real root cause is fixed.