skills.rest
BinyaminEden
BinyaminEdenCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Investigate root causes through a structured 4-phase workflow before code changes.

26|1|Updated Mar 19, 2026
Search Tags:#debugging#anti-patterns#root cause analysis#bug fixing#test failure#systematic debugging#production outage
One-click install
npx skills add https://github.com/BinyaminEden/claude-combine --skill systematic-debugging-binyamineden
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/BinyaminEden/claude-combine/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/BinyaminEden/claude-combine --skill systematic-debugging-binyamineden

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the wasted time, recurring bugs, and team frustration caused by random, symptom-focused fixes that mask underlying issues, even when under extreme time pressure or facing seemingly obvious quick solutions.

Core Features & Use Cases

  • Structured 4-Phase Workflow: Guides you through root cause investigation, pattern analysis, hypothesis testing, and controlled implementation to ensure fixes address the true source of issues.
  • Pressure-Resistant Guardrails: Uses explicit "ALWAYS"/"NEVER" rules, anti-pattern guidance, and mandatory checkpoints to prevent rationalizing shortcuts during emergencies or when exhausted.
  • Supporting Techniques: Includes ready-to-use guidance for root cause tracing, defense-in-depth validation, and condition-based waiting to resolve common debugging scenarios like flaky tests or deep call stack errors.
  • Use Case Example: For a failing production payment processing test, follow the process to trace the root cause of stale status updates instead of adding arbitrary timeouts that mask the underlying race condition.

Quick Start

Use the systematic-debugging skill to investigate the root cause of the failing payment processing test 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 fix recurring bugs caused by symptom-focused quick patches?▼

Recurring bugs from symptom-focused patches require systematic debugging that enforces mandatory root cause investigation before any code changes. A structured 4-phase workflow traces the true source of issues, eliminating wasted time and preventing random fixes from masking underlying problems.

What's the best way to debug a production outage under extreme time pressure?▼

Debugging a production outage under pressure requires pressure-resistant guardrails using explicit ALWAYS and NEVER rules with mandatory checkpoints. These guardrails prevent rationalizing shortcuts during emergencies, ensuring fixes address the actual root cause rather than obvious quick solutions.

How do I stop flaky tests from failing intermittently without adding arbitrary timeouts?▼

Stopping flaky test failures requires root cause tracing techniques instead of adding arbitrary timeouts that mask underlying race conditions. Systematic debugging provides supporting techniques like condition-based waiting and defense-in-depth validation to resolve intermittent test failures correctly.

Why does my bug fix keep causing new issues in my codebase?▼

Bug fixes causing new issues indicate symptom-focused random fixes that mask underlying root causes. Systematic debugging enforces pattern analysis and hypothesis testing through a structured workflow, ensuring first-time correct resolutions that eliminate recurring bugs and team frustration.

Can I use systematic debugging for build failures and performance degradation?▼

Systematic debugging applies to all technical issues including build failures, performance degradation, test failures, production outages, and integration errors. The structured root cause investigation process works across any technical context, particularly after multiple failed quick fixes.

When should I avoid quick fixes during root cause analysis?▼

Avoid quick fixes whenever anti-pattern guidance and mandatory checkpoints detect conditions like time pressure or exhaustion that rationalize shortcuts. Systematic debugging enforces controlled implementation after hypothesis testing, preventing premature fixes from masking the true source of issues.

Related Skills

Explore More Software Engineering Skills→
allexcdallexcd

autonomous-bug-fixing

Diagnose, reproduce, and fix code defects from bug reports or error logs.

Community
Advanced
alexanderopalexanderop
4

systematic-debugging

Diagnose software bugs through a four-phase root-cause investigation process.

Community
Basic
cookeyholdercookeyholder

systematic-debugging

Identify and resolve technical issues through a four-phase root-cause debugging workflow.

Community
Advanced
HerxinsasaHerxinsasa
1

systematic-debugging

Investigate root causes through a structured 4-phase debugging workflow.

Community
Advanced