skills.rest
alex-tgk
alex-tgkCOMMUNITY
Explore all skills by this author →
𝕏@acarr_techGitHub

Systematic Debugging

Enforce root-cause investigation before fixes with a four-phase debugging process.

1|Updated Oct 31, 2025
Search Tags:#testing#debugging#anti-patterns#systematic#phases#root-cause
One-click install
npx skills add https://github.com/alex-tgk/saasquatch --skill systematic-debugging-alex-tgk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Systematic Debugging
Source: https://github.com/alex-tgk/saasquatch/tree/main/.claude/skills/debugging/systematic-debugging
Command: npx skills add https://github.com/alex-tgk/saasquatch --skill systematic-debugging-alex-tgk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined, four-phase process that ensures root-cause investigation before attempting fixes, preventing symptom-driven patches.

Core Features & Use Cases

  • Four-phase framework: Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
  • Anti-shortcuts guidance and structured guardrails to resist time-pressure rationalization.
  • Works across bug reports, test failures, production incidents, and complex multi-service systems.

Quick Start

Load the systematic debugging skill and follow Phase 1 before proposing 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 instead of just patching symptoms?▼

Systematic debugging enforces root-cause investigation before any fixes by applying a structured four-phase process, preventing symptom-driven patches under pressure.

What is the best way to debug production incidents across multi-service systems?▼

A structured debugging framework with explicit gating and anti-pattern guidance handles production incidents across multi-service systems by ensuring pattern analysis precedes implementation.

How do I stop making symptom-driven fixes when facing time pressure during test failures?▼

Structured guardrails and anti-shortcut guidance resist time-pressure rationalization by gating fixes until hypothesis testing confirms the root cause of test failures.

Can I apply a systematic debugging process to any software project or team?▼

Yes, the four-phase framework applies to any bug, test failure, or unexpected behavior across software projects, teams, and production incidents without environment restrictions.

What are the four phases of systematic debugging?▼

The phases are Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation, with explicit gating at Phase 1 before proposing any changes.

Why do my bug fixes keep recurring as new issues in complex systems?▼

Recurring bugs indicate symptom-driven patches; enforcing root-cause investigation through pattern analysis and hypothesis testing before implementation breaks this cycle.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
aist-ai-sastaist-ai-sast

mcp-regression-fix

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

Official
Advanced
Donaldshen27Donaldshen27

systematic-debugging

Identify bug root causes through a four-phase systematic debugging framework.

Community
Advanced
UlanxxUlanxx

canary

Monitor live URLs for console errors, performance regressions, and page failures.

Community
Advanced