skills.rest
HerbertJulio
HerbertJulioCOMMUNITY
Explore all skills by this author →
GitHub

debug

Guide developers through a four-phase debugging workflow from evidence gathering to validation.

20|3|Updated Feb 22, 2026
Search Tags:#workflow#debugging#evidence#hypothesis#root-cause#bug
One-click install
npx skills add https://github.com/HerbertJulio/specialist-agent --skill debug-herbertjulio
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/HerbertJulio/specialist-agent/tree/main/skills/debug
Command: npx skills add https://github.com/HerbertJulio/specialist-agent --skill debug-herbertjulio

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Investigate and fix bugs, test failures, unexpected behavior, or errors by following a structured four-phase approach before proposing fixes.

Core Features & Use Cases

  • Four-phase debugging workflow: Gather Evidence, Analyze Patterns, Formulate Hypotheses, Implement & Prove; use for reproducible bug fixes, QA passes, and post-mortem analysis.
  • Evidence collection, hypothesis-driven debugging, and safe implementation verification with checkpoints.

Quick Start

Describe the bug and I will guide you through the four phases to identify and fix the root cause.

Frequently Asked Questions about debug

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

FAQPage Schema
What is a systematic debugging workflow for fixing software bugs?▼

A systematic debugging workflow guides developers through evidence gathering, pattern analysis, hypothesis formulation, and safe implementation to identify root causes and fix bugs reproducibly. It prevents trial-and-error guessing by enforcing structured checkpoints.

How do I debug unexpected software behavior or test failures step by step?▼

Debug unexpected behavior by following four phases: gather evidence, analyze patterns, formulate hypotheses, and implement fixes with validation. This structured approach ensures reproducible bug fixes and thorough post-mortem analysis.

Does hypothesis-driven debugging work without version control?▼

Hypothesis-driven debugging requires a structured environment and version control. Version control enables safe implementation verification and explicit checkpoints, ensuring fixes can be validated and rolled back without risking the project state.

What is the best way to find a root-cause bug fix instead of patching symptoms?▼

The best way to find a root-cause bug fix is using a four-phase workflow that moves from evidence collection to pattern analysis before implementation. This ensures you test hypotheses and prove fixes rather than patching symptoms.

Why does my debugging process fail to produce reproducible bug fixes?▼

Debugging fails to produce reproducible fixes when it skips evidence collection and hypothesis testing. Applying a structured workflow with explicit checkpoints for analysis and validation ensures fixes are proven and repeatable.

Related Skills

Explore More Software Engineering Skills→
mdmagnuson-creatormdmagnuson-creator

builder-delegation

Delegate tasks to sub-agents with structured context and pre-delegation checks.

Community
Advanced
allexcdallexcd

autonomous-bug-fixing

Diagnose, reproduce, and fix code defects from bug reports or error logs.

Community
Advanced
JeremyDev87JeremyDev87
31

error-analysis

Classify errors, interpret stack traces, and plan remediation steps.

Community
Advanced
rafaelcallejarafaelcalleja
2

systematic-debugging

Diagnose software issues using a four-phase systematic debugging framework.

Community
Basic