debug

Enforce a four-phase debugging workflow for systematic root-cause analysis.

2|1|Updated Feb 9, 2026

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

Ready to run

npx skills add https://github.com/costa-marcello/skillkit --skill debug-costa-marcello

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/costa-marcello/skillkit/tree/main/skills/Debug
Command: npx skills add https://github.com/costa-marcello/skillkit --skill debug-costa-marcello

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Guides engineers to diagnose bugs systematically by enforcing a four-phase workflow that surfaces root causes rather than patching symptoms.

Core Features & Use Cases

Enforces a four-phase debugging workflow (Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, Implementation) to guide consistent, evidence-based fixes.
Includes anti-patterns, references, and defensible practices to resist time-pressure shortcuts.
Supports multi-layer defense-in-depth and stack-trace tracing to trace data flows from symptom to source.

Quick Start

Begin with Phase 1: perform root-cause investigation, reproduce the issue, and gather evidence before moving to Phase 2.

Frequently Asked Questions about debug

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

FAQPage Schema

What is the best way to find the root cause of a production issue instead of patching symptoms?▼

Root-cause debugging requires a systematic four-phase workflow that enforces evidence gathering and reproduction before pattern analysis, preventing fix-at-symptom shortcuts under time pressure.

How do I debug test failures systematically without jumping to conclusions?▼

Debug test failures by strictly following Phase 1 root-cause investigation to reproduce the issue and gather evidence, then apply a single-hypothesis approach to test and validate fixes methodically.

Can I use a systematic debugging process for performance problems and integration challenges?▼

Systematic debugging applies directly to performance problems and integration challenges by using stack-trace tracing and multi-layer defense-in-depth to trace data flows from symptom to source.

How does a single-hypothesis approach work during root-cause investigation?▼

A single-hypothesis approach isolates one variable at a time during the Hypothesis and Testing phase, ensuring evidence-based validation before moving to the Implementation phase of the debugging workflow.

When should I not use defense-in-depth debugging patterns?▼

Avoid defense-in-depth debugging when time pressure forces bypassing Phase 1 evidence gathering, as skipping the strict four-phase workflow leads to patching symptoms rather than resolving the actual root cause.