skills.rest
tstapler
tstaplerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

Systematic Debugging

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

8|2|Updated Jul 13, 2015
Search Tags:#testing#debugging#anti-patterns#systematic#phases#hypothesis#root-cause
One-click install
npx skills add https://github.com/tstapler/dotfiles --skill systematic-debugging-tstapler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Systematic Debugging
Source: https://github.com/tstapler/dotfiles/tree/main/.claude/skills/debugging/systematic-debugging
Command: npx skills add https://github.com/tstapler/dotfiles --skill systematic-debugging-tstapler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined, four-phase framework to ensure root-cause investigation before proposing fixes, reducing wasted time on symptom patches and firefighting.

Core Features & Use Cases

  • Enforces Phase 1–4 discipline with explicit stop conditions, preventing shortcuts under pressure.
  • Guides teams through evidence gathering, pattern analysis, hypothesis testing, and safe implementation.
  • Use Case: apply the workflow to bugs, test failures, production incidents, performance problems, and integration issues to reliably identify root causes.

Quick Start

Follow this systematic debugging workflow on your next bug to ensure root-cause investigation before fixes.

Frequently Asked Questions about Systematic Debugging

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

FAQPage Schema
How do I find the root cause of a bug instead of just fixing the symptom?▼

Root-cause debugging enforces a four-phase discipline of evidence gathering, pattern analysis, hypothesis testing, and safe implementation to ensure you identify the actual cause before applying fixes.

What is the best way to debug production incidents systematically?▼

Systematic debugging provides a four-phase framework with explicit stop conditions to guide teams through diagnostic evidence collection and hypothesis testing, preventing firefighting and shortcuts under pressure during production incidents.

Can I apply a systematic debugging workflow to performance problems and test failures?▼

Yes, this systematic debugging workflow applies to bugs, test failures, production incidents, performance problems, and integration issues across any technology stack to reliably identify root causes.

How do I stop patching symptoms when debugging code under pressure?▼

By enforcing Phase 1–4 discipline with explicit stop conditions, systematic debugging prevents shortcuts under pressure, ensuring you complete root-cause investigation and hypothesis testing before implementing fixes.

When should I use hypothesis testing in my debugging workflow?▼

Hypothesis testing is Phase 3 of systematic debugging, performed after gathering diagnostic evidence and analyzing patterns, to validate potential root causes before you move to safe implementation of the fix.

Related Skills

Explore More Software Engineering Skills→
diegosouzapwdiegosouzapw
108

debugging

Automate structured debugging workflows to reproduce, diagnose, and verify software bug fixes.

Community
Advanced
aist-ai-sastaist-ai-sast

mcp-regression-fix

Diagnose MCP regression failures and implement durable fixes across test suites.

Official
Advanced
UnicornUnicorn

analyzer-agent

Perform read-only static analysis and security scanning of codebases.

Official
Advanced
Chikage0o0Chikage0o0
34

systematic-debugging

Enforce a four-phase root-cause debugging process for test failures and errors.

Community
Advanced