skills.rest
leessju
leessjuCOMMUNITY
Explore all skills by this author →
GitHub

debug-root

Diagnose recurring software bugs through a structured six-phase workflow.

Updated Apr 11, 2026
Search Tags:#debugging#diagnosis#code-quality#root-cause#bug-tracking#phase-workflow#repeat-bug
One-click install
npx skills add https://github.com/leessju/claude-skills --skill debug-root
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug-root
Source: https://github.com/leessju/claude-skills/tree/main/debug-root
Command: npx skills add https://github.com/leessju/claude-skills --skill debug-root

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams diagnose root causes when the same bug is fixed multiple times but the issue reoccurs, guiding a disciplined six-phase workflow instead of ad-hoc fixes.

Core Features & Use Cases

  • Freeze phase: inventory all prior changes without making new ones and infer why each attempt failed.
  • Trace phase: read code paths and data flows without executing the program to validate entry points and paths.
  • Diagnose phase: specify a concrete file/line-level root cause with supporting evidence.
  • Challenge phase: test counterfactuals and strengthen the diagnosis.
  • Fix phase: apply minimal, targeted changes only once.
  • Verify phase: explain why the fix resolves the symptom and cover edge cases. Use case: when a bug has been fixed multiple times but reappears, this skill provides a repeatable diagnosis and corrective workflow.

Quick Start

Describe the repeated-bug symptom, then drive through the six-phase workflow to isolate and fix the root cause.

Frequently Asked Questions about debug-root

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

FAQPage Schema
How do I find the root cause of a recurring bug that keeps reappearing after multiple fixes?▼

A recurring bug requires a structured debugging workflow that inventories prior failed fixes, traces code paths without execution, and specifies a concrete file-level root cause with supporting evidence before applying a targeted fix.

What is the best way to debug code when repeated fixes fail to prevent the issue?▼

Stop making ad-hoc changes and follow a disciplined diagnosis workflow that freezes prior attempts, traces data flows, challenges counterfactuals, and applies a minimal targeted fix only once to break the repeat-bug cycle.

How do I trace code paths and data flows without executing the program to validate entry points?▼

Trace code paths by reading source code statically to validate entry points and data flows, isolating the exact file and line-level root cause before making new changes.

When do I need a structured phase workflow for bug tracking and diagnosis?▼

You need a structured phase workflow for bug tracking when the same symptom reappears after multiple fixes, requiring evidence-based diagnosis and traceability instead of isolated patches.

Does evidence-based diagnosis work for complex software projects with stubborn bugs?▼

Yes, evidence-based diagnosis works for complex software projects by enforcing traceability across six phases, ensuring you specify concrete file-level root causes and verify edge cases before finalizing the fix.

Related Skills

Explore More Software Engineering Skills→
sQVesQVe

debug-issue

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

Community
Advanced
viraatdasviraatdas

investigate

Identify bug root causes by collecting symptoms, reading code, and testing hypotheses.

Community
Advanced
deonmenezesdeonmenezes
482

code-understanding

Map architecture, trace data flows, and hunt vulnerability variants in code.

Community
Advanced
burgebjburgebj

octopus-quick

Execute small software changes with atomic commits and state tracking.

Community
Intermediate