systematic-debugging

Name: systematic-debugging
Availability: InStock
Author: joshua3403

Guide engineers through a four-phase root-cause debugging workflow.

Updated Feb 2, 2026

Search Tags:#debugging #anti-patterns #troubleshooting #defense-in-depth #root-cause #four-phases

Ready to run

npx skills add https://github.com/joshua3403/giit-template --skill systematic-debugging-joshua3403

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/joshua3403/giit-template/tree/main/.agent/skills/systematic-debugging
Command: npx skills add https://github.com/joshua3403/giit-template --skill systematic-debugging-joshua3403

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured, repeatable debugging methodology that prevents symptom-focused fixes and accelerates identification of root causes.

Core Features & Use Cases

Four-phase workflow (Root Cause Investigation → Pattern Analysis → Hypothesis and Testing → Implementation) that guides the debugging process.
Anti-patterns and defensive practices (STOP and re-analyze, NEVER fix symptoms, defense-in-depth) to improve reliability under pressure.
Practical guidance for production bugs, failing tests, performance issues, and integration faults.

Quick Start

Load the Systematic Debugging skill, read the overview, and follow the Phase 1 Root Cause Investigation checklist first. If you feel pressure to rush, refer to the anti-patterns to resist shortcuts, then complete all four phases before implementing fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

How do I debug complex production bugs without just fixing the symptoms?▼

Debugging production bugs requires a systematic root-cause workflow that mandates complete investigation before implementing fixes, applying anti-patterns and defense-in-depth to prevent symptom-focused shortcuts.

What is the best way to troubleshoot failing tests and integration faults systematically?▼

Troubleshooting failing tests and integration faults follows a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation, ensuring structured verification throughout.

Why does my debugging process keep missing the root cause of performance problems?▼

Debugging performance problems misses root causes when engineers skip the investigation phase; a systematic approach enforces complete Root Cause Investigation and pattern analysis before any fixes.

How do I identify root causes of technical issues under pressure to rush a fix?▼

Identifying root causes under pressure requires following prescribed anti-patterns like STOP and re-analyze, ensuring you complete the Root Cause Investigation phase before moving to hypothesis testing or implementation.

Can I use a systematic debugging workflow for any type of technical issue?▼

A systematic debugging workflow applies to any technical issue including production bugs, failing tests, performance problems, and integration faults, guiding engineers through four phases from investigation to implementation.

When should I not use a root-cause debugging methodology?▼

Root-cause debugging methodology should not be used when a quick symptom patch is required for immediate mitigation, as the workflow strictly mandates complete investigation and structured verification before any implementation.