debugging

Enforce root-cause analysis before implementing fixes in software debugging.

8|2|Updated Jul 13, 2015

Search Tags:#debugging #defense-in-depth #verification #systematic #root-cause #traceback

Ready to run

npx skills add https://github.com/tstapler/dotfiles --skill debugging-tstapler

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/tstapler/dotfiles/tree/main/.claude/skills/debugging
Command: npx skills add https://github.com/tstapler/dotfiles --skill debugging-tstapler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Solve unproductive bug fixing by enforcing root-cause analysis before implementing any fixes.

Core Features & Use Cases

Provides a disciplined four-phase debugging process (root-cause investigation, pattern analysis, hypothesis testing, implementation) to prevent symptom-only fixes.
Integrates with related skills like root-cause tracing, defense-in-depth validation, and verification-before-completion to strengthen robustness.
Helps teams reduce MTTR and avoid regression by ensuring fixes address the true source of problems.

Quick Start

Apply the four-phase debugging framework to reproduce, analyze, hypothesize, and implement the root-cause fix in your codebase.

Frequently Asked Questions about debugging

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

FAQPage Schema

How do I enforce root-cause analysis before implementing software bug fixes?▼

Root-cause debugging prevents symptom-only fixes by enforcing a four-phase workflow: root-cause investigation, pattern analysis, hypothesis testing, and implementation. This structured process ensures the true source of problems is addressed.

What is the best way to reduce MTTR for production bugs and test failures?▼

To reduce Mean Time To Resolution for production bugs and test failures, apply a systematic four-phase debugging framework. Reproducing, analyzing, and hypothesizing root causes before implementation avoids regressions and accelerates resolution.

How do I systematically debug unexpected behavior using a structured workflow?▼

Systematically debug unexpected behavior by following a disciplined four-phase process: investigate root causes, analyze patterns, test hypotheses, and implement fixes. Multi-layer validation and verification before completion ensure robustness.

Can I use defense-in-depth validation for software engineering debugging?▼

Defense-in-depth validation integrates directly into the debugging workflow to strengthen robustness. It ensures multi-layer validation and verification before completion, preventing regressions and confirming fixes address the true source.

Why does fixing a traceback often result in recurring regressions?▼

Fixing a traceback often causes regressions when only symptoms are patched without root-cause analysis. Implementing a structured debugging process with hypothesis testing and verification before completion ensures the true source is resolved.

When do I need a systematic debugging process for software engineering tasks?▼

A systematic debugging process is needed whenever facing unproductive bug fixing, such as test failures, production bugs, or unexpected behavior. It enforces root-cause investigation and multi-layer validation to stop problems at the source.