skills.rest
KGmufassa
KGmufassaCOMMUNITY
Explore all skills by this author →
GitHub

systematic-debugger

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

Updated Aug 27, 2026
Search Tags:#debugging#defense-in-depth#traceability#root-cause#software-engineering#phased-workflow#testing-process
One-click install
npx skills add https://github.com/KGmufassa/Escrolly --skill systematic-debugger-kgmufassa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugger
Source: https://github.com/KGmufassa/Escrolly/tree/main/.opencode/skills/systematic-debugger
Command: npx skills add https://github.com/KGmufassa/Escrolly --skill systematic-debugger-kgmufassa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic Debugger helps teams stop patching symptoms and instead trace issues to their source, speeding up resolution and reducing rework.

Core Features & Use Cases

  • Phase-driven debugging process including Root Cause Investigation, Pattern Analysis, Hypothesis & Testing, and Implementation.
  • Use Case: apply to bugs across test, staging, and production environments, especially when issues span multiple components.
  • Quick-start guidance and references to proven tracing techniques for reliable diagnosis.

Quick Start

Begin Phase 1: reproduce the issue, collect evidence, and identify the root cause before any fixes.

Frequently Asked Questions about systematic-debugger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is root-cause debugging and when do I need it for multi-component systems?▼

Root-cause debugging is less effective for trivial, single-line syntax errors where the cause is immediately visible. It is designed for complex issues spanning multiple components where tracing and defense-in-depth analysis are required.

How do I systematically debug software bugs before proposing fixes?▼

Root-cause debugging is less effective for trivial, single-line syntax errors where the cause is immediately visible. It is designed for complex issues spanning multiple components where tracing and defense-in-depth analysis are required.

Does root-cause debugging work for production bugs and integration faults?▼

Root-cause debugging is less effective for trivial, single-line syntax errors where the cause is immediately visible. It is designed for complex issues spanning multiple components where tracing and defense-in-depth analysis are required.

What is the best way to stop patching symptoms and trace issues to their source?▼

Root-cause debugging is less effective for trivial, single-line syntax errors where the cause is immediately visible. It is designed for complex issues spanning multiple components where tracing and defense-in-depth analysis are required.

When should I not use a phased debugging workflow for software issues?▼

Root-cause debugging is less effective for trivial, single-line syntax errors where the cause is immediately visible. It is designed for complex issues spanning multiple components where tracing and defense-in-depth analysis are required.

Related Skills

Explore More Software Engineering Skills→
ssimhanssimhan
1

debugging

Reproduce software defects and verify fixes with evidence-based workflows.

Community
Basic
lv7devlv7dev

debugging

Investigate root causes before implementing fixes through a four-phase debugging workflow.

Community
Advanced
timurgaleevtimurgaleev
5

investigate

Guide structured root-cause debugging through phases for context, analysis, hypothesis, and verification.

Community
Advanced
mealpacmealpac
1

systematic-debugging

Enforce a four-phase root-cause debugging process for software tasks.

Community
Advanced