systematic-debugging

Guide root-cause investigation and phase-driven analysis for software bugs.

Updated Jun 20, 2026

Search Tags:#testing #debugging #defense-in-depth #trace #root-cause #pattern-analysis #repro

Ready to run

npx skills add https://github.com/lowmason/agent-skills --skill systematic-debugging-lowmason

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a structured approach to investigating and resolving bugs, preventing symptom fixes and promoting root-cause analysis.

Core Features & Use Cases

Phase-based framework: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation with guardrails.
Supports multi-component tracing, defense-in-depth, and evidence gathering to reduce rework and flaky failures.
Use cases include test failures, production bugs, performance regressions, and integration issues across projects.

Quick Start

Describe the issue, reproduce it reliably, gather cross-component evidence, and proceed with root-cause based fixes.

Frequently Asked Questions about systematic-debugging

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

FAQPage Schema

What is systematic debugging and when should I use it for software bugs?▼

Systematic debugging is a structured approach to investigating and resolving software bugs by finding root causes rather than fixing symptoms. Use it for test failures, production bugs, performance regressions, and complex multi-component integration issues.

How do I debug a production bug using root cause investigation?▼

To debug a production bug, describe the issue, reproduce it reliably, gather cross-component evidence, and proceed with phase-driven analysis. This enforces root cause investigation, pattern analysis, hypothesis testing, and implementation with guardrails to prevent symptom fixes.

Does systematic debugging work for multi-component tracing and infrastructure issues?▼

Yes, systematic debugging supports multi-component tracing across code, infrastructure, and integrations. It applies phase-driven analysis and evidence gathering to reduce rework and flaky failures in complex multi-component issues spanning your entire stack.

What is the best way to stop recurring test failures and flaky bugs?▼

The best way to stop flaky failures is applying defense-in-depth validation during the implementation phase of systematic debugging. By enforcing root cause investigation and evidence gathering before fixing, you prevent symptom patches that cause recurring test failures.

How does pattern analysis help fix performance regressions?▼

Pattern analysis helps fix performance regressions by identifying trends and commonalities across evidence gathered during root cause investigation. This phase-driven approach validates hypotheses before implementation, ensuring your performance fix targets the actual defect.

Can I use systematic debugging without being able to reproduce the bug?▼

Systematic debugging requires reliable reproduction as a quick start step before root cause investigation. Without a reproducible bug, you cannot effectively gather cross-component evidence or validate hypotheses to ensure your fix resolves the actual root cause.