skills.rest
HomericIntelligence
HomericIntelligenceOFFICIAL
Explore all skills by this author →
GitHub

systematic-debugging

Investigate root causes before proposing fixes in a four-phase debugging workflow.

6|Updated Dec 29, 2025
Search Tags:#debugging#troubleshooting#diagnostics#quality-assurance#phases#root-cause
One-click install
npx skills add https://github.com/HomericIntelligence/ProjectHephaestus --skill systematic-debugging-homericintelligence
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: systematic-debugging
Source: https://github.com/HomericIntelligence/ProjectHephaestus/tree/main/skills/systematic-debugging
Command: npx skills add https://github.com/HomericIntelligence/ProjectHephaestus --skill systematic-debugging-homericintelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Random fixes waste time and create new bugs. Always find root cause before attempting fixes.

Core Features & Use Cases

  • Phase-driven debugging with a four-phase workflow to identify root causes, gather evidence, and validate fixes.
  • Diagnostic instrumentation across component boundaries to trace data flow and verify environment/config propagation.
  • Clear guardrails and verification steps to stop remediation when root cause isn't established.

Quick Start

Begin Phase 1: Root Cause Investigation by inspecting the error, reproducing the issue, and gathering evidence before proposing 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 before attempting fixes?▼

Root cause debugging requires a four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis and Testing, and Implementation. You begin by inspecting the error, reproducing the issue, and gathering evidence before proposing any fixes.

What is the best way to debug multi-component integration issues?▼

Debugging multi-component integration issues requires diagnostic instrumentation across component boundaries to trace data flow and verify environment and configuration propagation, ensuring you establish root cause before applying changes.

How do I stop guessing and systematically troubleshoot production bugs?▼

Systematic troubleshooting enforces strict gating before changes, requiring root cause investigation and evidence gathering across four phases to prevent random fixes that waste time and create new bugs.

How do I debug performance problems using a phase-driven approach?▼

Debugging performance problems follows a phase-driven workflow that identifies root causes through pattern analysis and hypothesis testing, applying diagnostic instrumentation to validate fixes before implementation.

Does this debugging workflow work for test failures and unexpected behavior?▼

Yes, the root cause investigation workflow applies to test failures, production bugs, unexpected behavior, performance problems, and multi-component integration issues by enforcing evidence gathering and strict gating before changes.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

Diagnose bugs by tracing evidence and generating a BR issue template.

Community
Advanced
amrhas82amrhas82
21

systematic-debugging

Identify root causes in software bugs using a four-phase investigation framework.

Community
Basic
pproencapproenca

systematic-debugging

Trace data flow and verify root causes before implementing software fixes.

Community
Basic
kk20300113-pngkk20300113-png

investigate

Guide structured root-cause debugging for software errors and regressions.

Community
Advanced