skills.rest
yairbederman
yairbedermanCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Identify root causes of bugs through a four-phase investigation process.

Updated Dec 24, 2025
Search Tags:#debugging#verification#quality-assurance#reproduction#root-cause-analysis#hypothesis-testing
One-click install
npx skills add https://github.com/yairbederman/EngineeringAgency --skill systematic-debugging-yairbederman
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/yairbederman/EngineeringAgency/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/yairbederman/EngineeringAgency --skill systematic-debugging-yairbederman

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging reduces wasted effort by preventing symptom fixes and ensuring root-cause analysis before implementing any change.

Core Features & Use Cases

  • Four-phase process (Root Cause Investigation, Isolation, Hypothesis Testing, Implementation) ensures thorough analysis for any issue.
  • Emphasis on reproducibility, evidence gathering, and creating minimal reproductions to isolate triggers.
  • Applicable across production, staging, and development environments, including performance, integration, and build failures.

Quick Start

Execute Phase 1 through Phase 4 in order to resolve the issue by first identifying the root cause, then isolating and testing hypotheses, and finally implementing a safe fix.

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?▼

Root-cause debugging identifies the exact trigger of bugs by enforcing a four-phase process: investigation, isolation, hypothesis testing, and implementation. This prevents wasted effort on symptom fixes.

What is the best way to debug test failures across staging and production environments?▼

Systematic debugging applies across production, staging, and development environments by focusing on consistent reproduction, evidence collection, and creating minimal reproductions to isolate the trigger.

How do I isolate a bug trigger before attempting a fix?▼

You isolate a bug by creating minimal reproductions and gathering evidence during the isolation phase, ensuring the exact trigger is identified before moving to hypothesis testing and implementation.

Can I use this systematic debugging approach for build and integration failures?▼

Yes, the four-phase debugging process is applicable to performance, integration, and build failures, ensuring thorough analysis and minimal changes across varying system complexities.

Why should I test hypotheses before implementing a bug fix?▼

Hypothesis testing is a required phase that validates the isolated root cause before implementation. This ensures the proposed fix is safe and prevents applying unnecessary changes to the system.

Related Skills

Explore More Software Engineering Skills→
jk278jk278

debugging-assistant

Diagnose software bugs from stack traces and error logs.

Community
Advanced
a747895159a747895159

BUG 定位与修复

Diagnose and repair software bugs with root-cause analysis and validation.

Community
Advanced
bigeasyfreemanbigeasyfreeman
2

systematic-debugging

Debug code errors through evidence collection, hypothesis testing, and verification.

Community
Advanced
jpeggdevjpeggdev

root-cause

Guide a four-phase process to identify root causes of software bugs.

Community
Advanced