skills.rest
passionseed
passionseedOFFICIAL
Explore all skills by this author →
GitHub

systematic_debugging

Investigate root causes of bugs through a four-phase debugging workflow.

2|1|Updated Feb 26, 2026
Search Tags:#debugging#defense-in-depth#systematic#tracing#phases#root-cause
One-click install
npx skills add https://github.com/passionseed/ps_app --skill systematic-debugging-passionseed
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic_debugging
Source: https://github.com/passionseed/ps_app/tree/main/.agent/skills/systematic-debugging
Command: npx skills add https://github.com/passionseed/ps_app --skill systematic-debugging-passionseed

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a proven, four-phase approach to uncover root causes of bugs and failures before proposing any fixes, reducing time wasted on symptom fixes.

Core Features & Use Cases

  • Enforces a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation
  • Includes anti-patterns, defense-in-depth strategies, and explicit failure modes to resist rushed shortcuts
  • Offers practical references and real-world guidance for tracing data flows and validating fixes
  • Useful in debugging, test failures, production incidents, and complex system failures across software projects

Quick Start

Begin Phase 1, then progress through Phases 2–4 to diagnose root causes before implementing 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 do I need it for production incidents?▼

Systematic debugging is a structured approach to uncover root causes of software bugs and production incidents before applying fixes. You need it to reduce time wasted on symptom fixes during complex system failures and test failures.

How do I find the root cause of a bug before fixing it?▼

To find the root cause of a bug, follow a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation. This enforces tracing data flows and validating fixes before implementation.

What's the best way to debug complex system failures across software projects?▼

The best way to debug complex system failures is using a defense-in-depth strategy with explicit anti-patterns to resist rushed shortcuts. This approach enforces pattern analysis and hypothesis testing to validate root causes across software projects.

Does this debugging approach work for performance issues and test failures?▼

Yes, this debugging approach works for performance issues and test failures. It applies to diagnosing root causes across debugging scenarios, production incidents, and complex system failures in software projects by enforcing a four-phase workflow.

What are common anti-patterns and failure modes when diagnosing software bugs?▼

Common anti-patterns when diagnosing software bugs include taking rushed shortcuts and applying symptom fixes. This approach counters them with explicit failure modes, defense-in-depth checks, and structured hypothesis testing before implementation.

Related Skills

Explore More Software Engineering Skills→
derHakenderHaken
437

systematic-debugging

Trace data flow and apply a four-phase process to fix root causes.

Community
Advanced
dmulcaheydmulcahey

systematic-debugging

Trace software bugs to root causes using a four-phase investigation methodology.

Community
Advanced
AbdullahMalik17AbdullahMalik17
9

systematic-debugging

Identify root causes of bugs using a structured four-phase process.

Community
Advanced
docaohieu2808docaohieu2808

debug

Trace software defects through systematic investigation and root cause analysis.

Community
Advanced