skills.rest
zenobi-us
zenobi-usOFFICIAL
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Apply a four-phase structured framework to identify and eliminate root causes of bugs.

68|6|Updated Apr 16, 2020
Search Tags:#software engineering#debugging#root cause#problem solving#troubleshooting#incident response#system analysis
One-click install
npx skills add https://github.com/zenobi-us/dotfiles --skill systematic-debugging-zenobi-us
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/zenobi-us/dotfiles/tree/main/devtools/files/opencode/skills/systematic-debugging
Command: npx skills add https://github.com/zenobi-us/dotfiles --skill systematic-debugging-zenobi-us

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes and quick patches only mask symptoms, leading to wasted time, new bugs, and recurring issues. This Skill ensures you find and fix the true root cause every time.

Core Features & Use Cases

  • Four-Phase Framework: Guides through Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation.
  • Evidence-Based Debugging: Mandates gathering diagnostic evidence and tracing data flow before proposing any fixes.
  • Architectural Questioning: Provides a critical checkpoint to question architecture if multiple fixes fail, preventing endless symptom-chasing.
  • Use Case: Your production system is experiencing intermittent failures. Use this Skill to systematically investigate the issue, trace data flow across components, form a single hypothesis, and implement a verified fix that addresses the true root cause.

Quick Start

Use the systematic-debugging skill to investigate a 'Connection timeout' error in your payment processor, starting with careful error message analysis.

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 analysis requires a structured four-phase framework: investigate the error systematically, analyze patterns across failures, test hypotheses against evidence, then implement a verified fix. This approach prevents recurring issues and wasted time on temporary patches.

What's the best way to debug production failures and intermittent errors?▼

Gather diagnostic evidence and trace data flow across components before proposing fixes. Systematic debugging mandates evidence collection, architectural questioning if multiple fixes fail, and completion of investigation phases before implementation to address true causes.

How do I troubleshoot test failures, performance problems, and integration issues systematically?▼

Apply a four-phase debugging process covering root cause investigation, pattern analysis, hypothesis testing, and implementation. This framework handles technical issues across test failures, performance degradation, and build failures with structured problem-solving.

Why do quick fixes create more bugs and how do I avoid that trap?▼

Random patches mask symptoms without addressing underlying causes, leading to new bugs and recurring issues. Systematic debugging enforces evidence-based investigation and architectural review to resist time-pressure shortcuts and ensure lasting fixes.

Can I use this debugging approach for incident response and system analysis?▼

Yes. The framework applies across incident response, system analysis, and troubleshooting. It guides you through mandatory Phase 1 completion, explicit root-cause focus, and anti-pattern defenses to solve technical problems comprehensively.

Related Skills

Explore More Software Engineering Skills→
k1lgork1lgor
2

observability-specialist

Collect logs, metrics, and traces to monitor system health.

Community
Intermediate
mkalkeremkalkere
4

debugging

Reproduce, isolate, and diagnose code failures with evidence-based techniques.

Community
Advanced
gajjalaashok75-UIgajjalaashok75-UI
2

error-detective

Extract error patterns from logs and stack traces to identify root causes.

Community
Advanced
mmbianco78mmbianco78

root-cause-tracing

Trace software errors backward to their root cause before deployment.

Community
Basic