skills.rest
HadiCherkaoui
HadiCherkaouiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

systematic-debugging

Diagnose root causes of technical issues through a four-phase debugging workflow.

Updated Apr 16, 2026
Search Tags:#debugging#defense-in-depth#phases#root-cause#pattern-analysis#hypothesis-testing#data-trace
One-click install
npx skills add https://github.com/HadiCherkaoui/opencode-config --skill systematic-debugging-hadicherkaoui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/HadiCherkaoui/opencode-config/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/HadiCherkaoui/opencode-config --skill systematic-debugging-hadicherkaoui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic Debugging provides a disciplined approach to diagnosing bugs and unexpected behavior, ensuring root causes are identified before fixes to reduce wasted time and rework.

Core Features & Use Cases

  • Four-phase workflow: root-cause investigation, pattern analysis, hypothesis testing, and implementation, with built-in defense-in-depth checks.
  • Comprehensive data-flow tracing: identify where bad data originates and how it propagates across components to locate the true trigger.
  • Risk-averse execution: prevents premature fixes, encourages evidence-based decisions, and accelerates reliable resolution for bugs, test failures, and production issues.

Quick Start

Begin with Phase 1: read errors, reproduce consistently, and trace data flow to identify the root cause before attempting 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?▼

Root-cause investigation identifies the true trigger of a bug by tracing data flow and reproducing errors consistently before attempting fixes. This systematic debugging approach enforces evidence-based decisions to prevent rework and wasted time.

What is the best way to debug production bugs and test failures methodically?▼

A disciplined four-phase workflow of root-cause investigation, pattern analysis, hypothesis testing, and implementation resolves production bugs and test failures. Diagnostic tracing maps where bad data originates and how it propagates across components.

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

Yes, systematic debugging applies to any technical issue across codebases, including performance problems, build failures, and integration failures. It enforces risk-averse execution with defense-in-depth checks for reliable resolution.

How does hypothesis testing work when diagnosing codebase issues?▼

Hypothesis testing validates potential root causes during the debugging workflow before implementing actual fixes. This phase follows pattern analysis to ensure evidence-based decisions and prevent premature code changes.

Why should I trace data flow when diagnosing unexpected behavior in my code?▼

Tracing data flow locates where bad data originates and how it propagates across components to find the true trigger. This comprehensive diagnostic tracing prevents premature fixes by ensuring the root cause is identified first.

Does systematic debugging prevent premature fixes during root-cause investigations?▼

Yes, systematic debugging enforces risk-averse execution that prevents premature fixes by requiring evidence-based decisions. The four-phase workflow ensures root causes are fully investigated and validated through hypothesis testing before implementation.

Related Skills

Explore More Software Engineering Skills→
tutur3ututur3u
53

systematic-debugging

Enforce root-cause investigation before fixing software bugs.

Official
Advanced
MovchanetsMovchanets

debugger

Diagnose software errors by tracing stack traces to root causes.

Community
Intermediate
CrumbgrabberCrumbgrabber
3

systematic-debugging

Implement a four-phase debugging framework to identify root causes before proposing fixes.

Community
Advanced
fmflurryfmflurry
171

src-dialog-read-error-resolution

Automate recurring dialog error-resolution workflows with capture, reproduction, patching, and verification.

Community
Intermediate