skills.rest
AndrewLi0420
AndrewLi0420COMMUNITY
Explore all skills by this author →
GitHub

debug

Identify and fix software failure root causes using logs, traces, and tests.

Updated Mar 18, 2026
Search Tags:#debugging#investigation#logging#root-cause#reproduction#pattern-analysis#hypothesis-testing
One-click install
npx skills add https://github.com/AndrewLi0420/BMW --skill debug-andrewli0420
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: debug
Source: https://github.com/AndrewLi0420/BMW/tree/main/.claude/skills/gstack/debug
Command: npx skills add https://github.com/AndrewLi0420/BMW --skill debug-andrewli0420

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Root-cause debugging guides engineers to identify and fix fundamental causes of software failures.

Core Features & Use Cases

  • Structured four-phase workflow: investigate, analyze, hypothesize, implement.
  • Evidence-based decision making with logging, traces, and tests.
  • Use case: when a flaky bug appears across modules, run the framework to pinpoint root cause and implement a regression-proof fix.

Quick Start

Describe the initial steps you would take to begin root-cause debugging for a reported issue.

Frequently Asked Questions about debug

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

FAQPage Schema
What is the best way to identify the root cause of a flaky bug across multiple modules?▼

Root-cause debugging identifies fundamental causes of software failures by guiding conversations from symptoms to verified fixes using logs, traces, and tests across modules. It enforces a four-phase workflow: investigate, analyze, hypothesize, and implement.

How do I structure a debugging investigation from initial symptom to verified fix?▼

Structure your debugging investigation by following the four-phase workflow: investigate symptoms, analyze collected evidence, hypothesize potential root causes, and implement regression-proof fixes. This ensures evidence-based decision making rather than speculative patching.

How does evidence-based debugging work when analyzing software failures?▼

Evidence-based debugging works by collecting concrete data from logs, traces, and tests during the investigation phase, then using that evidence to test hypotheses and validate root causes before implementing a documented final solution.

Can I use this structured debugging approach for issues across different team contexts?▼

Yes, this structured debugging approach applies across projects and team contexts, guiding collaborative conversations from reported symptoms to verified fixes regardless of the specific software environment or team structure involved.

When do I need a structured root-cause debugging workflow instead of ad-hoc troubleshooting?▼

You need a structured root-cause debugging workflow when flaky bugs appear across modules and ad-hoc troubleshooting fails to pinpoint the fundamental cause, requiring systematic evidence collection and hypothesis testing to implement regression-proof fixes.

Related Skills

Explore More Software Engineering Skills→
NTCodingNTCoding
334

observability-first-debugging

Instrument software with logs and traces to debug runtime behavior.

Community
Basic
bhianerdbhianerd
1

investigate

Guide root-cause debugging with evidence collection and hypothesis validation.

Community
Advanced
mwaymway
4

systematic-debugging

Identify root causes of bugs and test failures through a four-phase debugging workflow.

Community
Advanced
jnMetaCodejnMetaCode
7.6k

systematic-debugging

Identify root causes of bugs through a four-phase debugging workflow.

Community
Advanced