skills.rest
yckkkk
yckkkkCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugging

Trace root causes of technical bugs through a four-phase investigation workflow.

1|Updated May 6, 2026
Search Tags:#testing#debugging#investigation#defense-in-depth#phases#root-cause
One-click install
npx skills add https://github.com/yckkkk/reo --skill systematic-debugging-yckkkk
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/yckkkk/reo/tree/main/.agents/skills/systematic-debugging
Command: npx skills add https://github.com/yckkkk/reo --skill systematic-debugging-yckkkk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic debugging provides a disciplined approach to identify and trace root causes of bugs before applying fixes, reducing wasted effort on symptom-only patches and helping teams operate under time pressure without backsliding into guesswork.

Core Features & Use Cases

  • Phase-based workflow covering Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
  • Anti-patterns and guardrails that resist shortcut fixes and encourage thorough analysis.
  • Support for root-cause tracing, defense-in-depth practices, and structured decision making under pressure.
  • Real-world guidance on applying the method across test failures, production incidents, and complex multi-component systems.

Quick Start

Load the skill and follow Phase 1 through Phase 4 in order to identify 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 root-cause debugging and why is it necessary before applying fixes?▼

Root-cause debugging systematically traces the underlying cause of bugs before implementing fixes, reducing wasted effort on symptom-only patches and preventing recurring issues under time pressure.

How do I trace production bugs and test failures using a structured debugging workflow?▼

Trace production bugs and test failures by following a four-phase debugging workflow: root cause investigation, pattern analysis, hypothesis testing, and implementation, ensuring thorough analysis before any code changes.

Can I use this systematic debugging method for complex multi-component systems?▼

Yes, systematic debugging applies to complex multi-component systems, providing real-world guidance and structured decision-making to identify root causes across diverse technical issues and performance problems.

What is the best way to stop guesswork and shortcut fixes during incident investigation?▼

The best way to stop guesswork is using anti-pattern guardrails and defense-in-depth practices that resist shortcut fixes, enforcing structured analysis throughout the debugging process under time pressure.

How do I test a debugging hypothesis before implementing a code fix?▼

Test a debugging hypothesis during the dedicated hypothesis and testing phase, validating your root-cause analysis against the observed technical issue before moving to the implementation phase.

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
haJ1thaJ1t

systematic-debugging

Diagnose bugs to verified root cause using reproduce-minimize-hypothesize-bisect-confirm.

Community
Advanced
dhruvinrsonidhruvinrsoni

profiling-analysis

Analyze CPU and memory profiles and distributed traces to identify performance bottlenecks.

Community
Advanced
TumeloRamaphosaTumeloRamaphosa

systematic-debugging

Enforce root-cause investigation before proposing fixes in debugging workflows.

Community
Advanced