skills.rest
francoisbgdw
francoisbgdwCOMMUNITY
Explore all skills by this author →
GitHub

debug

Guide users through reproduce, investigate, hypothesize, fix, and verify phases.

Updated Mar 14, 2026
Search Tags:#workflow#investigation#troubleshooting#debug#root-cause#software-engineering
One-click install
npx skills add https://github.com/francoisbgdw/claude-skills --skill debug-francoisbgdw
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/francoisbgdw/claude-skills/tree/main/skills/debug
Command: npx skills add https://github.com/francoisbgdw/claude-skills --skill debug-francoisbgdw

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces disciplined, methodical debugging by requiring investigation before making changes, reducing blind fixes and regression risk.

Core Features & Use Cases

  • Structured phases: Reproduce, Investigate, Hypothesize, Fix, Verify.
  • Three-strike circuit breaker to avoid endless debugging loops.
  • Practical guidance for tracing root causes, reading stack traces, and documenting findings.

Use cases include when users report bugs, crashes, or unexpected behavior and need a repeatable debugging workflow.

Quick Start

Reproduce the bug, capture the exact error, then follow the five-phase debugging workflow 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
How do I debug a software crash by finding the root cause instead of just patching symptoms?▼

Root-cause debugging enforces investigation before fixes by guiding you through reproduce, investigate, hypothesize, fix, and verify phases to resolve software crashes at their source.

What is the best way to structure a debugging workflow for unexpected behavior across codebases?▼

A structured debugging workflow applies five phases—reproduce, investigate, hypothesize, fix, and verify—to methodically trace unexpected behavior across codebases and environments, reducing blind fixes and regression risk.

How do I stop endless debugging loops when troubleshooting a bug report?▼

A three-strike circuit breaker limits debugging iterations during troubleshooting, preventing endless loops and preserving debugging safety when bug reports require repeated investigation cycles.

Can I use a disciplined debugging workflow for any type of bug report or crash?▼

Disciplined debugging workflows apply to bug reports, crashes, and unexpected behavior across codebases and environments, requiring you to reproduce the bug and capture the exact error before starting.

Why does fixing a bug without investigating first lead to regression risk?▼

Debugging without investigation leads to regression risk because blind fixes bypass root-cause analysis, requiring structured hypotheses and verification to ensure the original error is resolved at its source.

What are the limitations of using a structured debugging workflow for software engineering?▼

Structured debugging workflows require strict adherence to investigation phases before fixes, and the three-strike circuit breaker may halt iterations before resolving complex crashes needing deeper analysis.

Related Skills

Explore More Software Engineering Skills→
iliaaliliaal
30

ia-debugging

Trace errors and regressions to root causes with evidence and regression tests.

Community
Advanced
first-flukefirst-fluke
1

oma-debug

Diagnose code bugs by guiding reproduction, root cause analysis, and regression testing.

Official
Advanced
26mitch2626mitch26

gstack-openclaw-investigate

Analyzes stack traces and errors to identify root causes of software bugs.

Community
Advanced
chicanoandres702chicanoandres702

debugger

Diagnose software defects by capturing errors, isolating failures, and verifying fixes.

Community
Intermediate