skills.rest
casualjim
casualjimCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Enforce root-cause investigation before fixes across four debugging phases.

3|5|Updated Apr 26, 2026
Search Tags:#testing#debugging#defense-in-depth#tracing#quality-assurance#root-cause#phase-based
One-click install
npx skills add https://github.com/casualjim/pi-superpowers --skill systematic-debugging-casualjim
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/casualjim/pi-superpowers/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/casualjim/pi-superpowers --skill systematic-debugging-casualjim

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and create new bugs. Always find the root cause before attempting fixes to prevent symptom-driven thrashing.

Core Features & Use Cases

  • Four-phase debugging framework (Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, Implementation) with explicit gates.
  • Guardrails and anti-patterns to resist time-pressure shortcuts and ensure data-flow tracing.
  • Works across development, CI, and production debugging scenarios; supports defense-in-depth and stack-trace instrumentation.

Quick Start

Start by performing Phase 1: Root Cause Investigation before attempting any 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 before attempting fixes?▼

Root-cause debugging enforces a four-phase investigation framework requiring you to complete Phase 1 before proposing fixes, preventing symptom-driven thrashing and wasted time.

What is the best way to debug production issues without causing new bugs?▼

A systematic debugging approach with explicit phase gates and guardrails resists time-pressure shortcuts, ensuring data-flow tracing and defense-in-depth for robust remediation across production scenarios.

How do I trace data flow and analyze patterns when debugging test failures?▼

The framework guides you through Root Cause Investigation and Pattern Analysis phases, using stack-trace instrumentation and data-flow tracing to identify failure patterns before forming testable hypotheses.

Does systematic debugging work for CI pipelines and integration challenges?▼

Yes, the four-phase framework works across development, CI, and production debugging scenarios, applying defense-in-depth and root-cause tracing to integration challenges and performance problems.

Why do random fixes create recurring bugs and how can I prevent it?▼

Random fixes waste time and create new bugs by treating symptoms instead of causes; enforcing root-cause investigation with anti-pattern guardrails before implementation prevents this recurring cycle.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
dmulcaheydmulcahey

systematic-debugging

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

Community
Advanced
fockusfockus
2

kaizen:root-cause-tracing

Trace bugs through call stacks to identify and remove root causes.

Community
Advanced
JBonfimJBonfim

no-workarounds

Enforce root-cause fixes over workarounds in software engineering tasks.

Community
Advanced