tool-systematic-debugging

Guide root-cause investigation through four structured debugging phases.

339|58|Updated Jan 10, 2026

Search Tags:#debugging #defense-in-depth #traceability #process #phases #root-cause

Ready to run

npx skills add https://github.com/Heyvhuang/ship-faster --skill tool-systematic-debugging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: tool-systematic-debugging
Source: https://github.com/Heyvhuang/ship-faster/tree/main/skills/tool-systematic-debugging
Command: npx skills add https://github.com/Heyvhuang/ship-faster --skill tool-systematic-debugging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill helps engineers reliably diagnose bugs by forcing root-cause analysis before fixes, reducing wasted effort and rework.

Core Features & Use Cases

Phase-driven debugging: Enforces Phase 1 through Phase 4 with explicit guardrails.
Defense-in-depth: Encourages multi-layer validation and explicit "stop and reanalyze" rules to avoid symptom fixes.
Trace-data driven: Provides techniques like root-cause tracing and event-based debugging.
Audit-ready artifacts: Maintains evidence trails and reproducible steps for review.

Quick Start

Load the skill in your agent's skills directory, read the overview, and begin with Phase 1: Root Cause Investigation, then progress through the subsequent phases before proposing any fixes.

Frequently Asked Questions about tool-systematic-debugging

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

FAQPage Schema

What is systematic debugging and how does root-cause analysis prevent recurring bugs?▼

Systematic debugging enforces root-cause investigation before fixes, reducing wasted effort and rework. It uses a structured four-phase approach to ensure reliable diagnosis and minimal blast radius, preventing symptom fixes that cause recurring bugs.

How do I debug a production outage or flaky test step by step to find the actual failure?▼

To debug a production outage or flaky test, progress through four phases: data gathering, pattern analysis, hypothesis testing, and safe implementation. This structured approach ensures you find the actual failure before deploying fixes.

Does this systematic debugging approach work for any technical issue or is it framework specific?▼

This systematic debugging approach applies to any technical issue, from flaky tests to production outages. It is not framework specific, using trace-data driven techniques like root-cause tracing and event-based debugging across all platforms.

What is defense-in-depth in debugging and when should I stop and reanalyze?▼

Defense-in-depth in debugging uses multi-layer validation and explicit stop-and-reanalyze rules to avoid symptom fixes. You should stop and reanalyze when hypothesis testing fails to confirm a root cause before proceeding to fixes.

How do I maintain traceability and audit-ready artifacts during root-cause investigation?▼

Maintain traceability and audit-ready artifacts during root-cause investigation by keeping evidence trails and reproducible steps for review. The structured phases enforce data gathering and pattern analysis to generate these audit records.

Why does applying quick fixes without a debugging process lead to larger production blast radius?▼

Applying quick fixes without a debugging process leads to a larger production blast radius because symptom fixes bypass root-cause investigation. Systematic debugging enforces defense-in-depth checks to ensure minimal blast radius when deploying fixes.