skills.rest
lv7dev
lv7devCOMMUNITY
Explore all skills by this author →
GitHub

debugging

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

Updated Feb 3, 2026
Search Tags:#debugging#defense-in-depth#verification#systematic#phases#root-cause
One-click install
npx skills add https://github.com/lv7dev/shop_v2 --skill debugging-lv7dev
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/lv7dev/shop_v2/tree/main/.claude/skills/debugging
Command: npx skills add https://github.com/lv7dev/shop_v2 --skill debugging-lv7dev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a disciplined framework for debugging that ensures root-cause investigation before coding fixes, reducing wasted time on symptom-only patches and rework.

Core Features & Use Cases

  • Four-phase workflow: Root Cause Investigation, Pattern Analysis, Hypothesis Testing, and Implementation, with explicit "no fixes without root cause" rule.
  • Evidence-driven debugging: Promotes reproducible steps, data gathering, and cross-checking against references to verify changes.
  • When to use: Ideal during any bug, test failure, or unexpected behavior where a reliable fix is required.

Quick Start

Run through Phase 1: read error messages and reproduce the issue before proposing changes, then proceed to Phase 2 only after evidence collection.

Frequently Asked Questions about 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 fixing the symptom?▼

To perform root-cause debugging, you must first gather evidence by reading error messages and reproducing the issue, then analyze patterns and test hypotheses before implementing a verified fix.

What is the best way to systematically debug a failing test or unexpected behavior?▼

Systematic debugging requires evidence-driven steps: reproduce the issue, gather data, cross-check against references, and test hypotheses to ensure a reliable resolution rather than a symptom-based patch.

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

Use systematic debugging during any bug, test failure, or unexpected behavior where reliable resolution is required, especially when root-cause analysis is needed to prevent future rework.

Why do my code fixes keep causing rework or recurring test failures?▼

Symptom-based patches cause rework because they skip root-cause investigation; applying a disciplined debugging framework ensures you identify the actual failure origin before changing code.

Can I apply hypothesis testing before implementing a bug fix?▼

Yes, the debugging workflow includes a dedicated Hypothesis Testing phase that requires you to validate assumptions and verify evidence before moving into the Implementation phase.

Related Skills

Explore More Software Engineering Skills→
seanGSISGseanGSISG
3

systematic-debugging

Diagnose software bug root causes through four investigation phases.

Community
Basic
robkamrobkam
12

bugfix-red-green-proof

Enforce a red-green-proof loop starting with a failing regression test.

Community
Advanced
randalmurphalrandalmurphal

debugging-strategies

Trace root causes through call stacks with pdb, debugpy, and logging analysis.

Community
Advanced
leonanpereirapintoleonanpereirapinto
1

no-workarounds

Enforce root-cause fixes by detecting and rejecting workaround patterns in code.

Community
Advanced