debugging

Diagnose defects through a four-phase root-cause debugging framework.

24|3|Updated Nov 25, 2025

Search Tags:#testing #debugging #troubleshooting #reproduce #errors #root-cause

Ready to run

npx skills add https://github.com/nguyenthienthanh/aura-frog --skill debugging-nguyenthienthanh

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: debugging
Source: https://github.com/nguyenthienthanh/aura-frog/tree/main/aura-frog/skills/debugging
Command: npx skills add https://github.com/nguyenthienthanh/aura-frog --skill debugging-nguyenthienthanh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Systematic debugging framework that centers root-cause investigation before applying fixes, reducing wasted effort and preventing regression.

Core Features & Use Cases

Four-Phase Process: Investigate → Analyze → Hypothesize → Fix assure changes address root cause.
Verification Protocol: Run tests, review outputs, and verify results before declaring completion.
Red Flags: Recognize patterns that require revisiting the investigation phase.
References: Deep-dive docs to enhance debugging discipline.

Quick Start

Apply the four-phase debugging workflow on a failing test to identify the root cause before implementing a fix.

Frequently Asked Questions about debugging

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

FAQPage Schema

How do I debug a failing test to find the root cause?▼

Root-cause debugging involves a four-phase workflow: Investigate the failure by examining logs and stack traces, Analyze the evidence to understand what happened, Hypothesize the underlying defect, then Fix and verify the change. This systematic approach prevents blind fixes and ensures solutions address the actual problem, not just symptoms.

What's the best way to troubleshoot runtime errors and unexpected behavior?▼

Troubleshooting runtime errors requires capturing error output, reproducing the issue consistently, gathering evidence from logs and git history, and analyzing what changed. The debugging framework guides you through each phase to isolate the defect before implementing a fix, reducing wasted debugging effort.

How do I reproduce and diagnose build problems?▼

Reproducing build problems starts by capturing the error output and environment details, then systematically analyzing logs and recent changes. The four-phase framework helps you identify whether the issue stems from dependencies, configuration, code changes, or environment setup before attempting a fix.

Why does my performance issue keep coming back after I fix it?▼

Performance issues recur when fixes address symptoms rather than root causes. Root-cause debugging prevents this by requiring you to investigate the underlying defect, gather performance evidence, and hypothesize the true bottleneck before implementing changes, with verification to confirm the fix is effective.

What are red flags that indicate I need to restart my debugging investigation?▼

Red flags include fixes that work inconsistently, errors reappearing after deployment, or changes that seem unrelated to the symptoms. The framework recognizes these patterns as signals to revisit the investigation phase and gather more evidence rather than proceeding with incomplete analysis.

How do I verify that my bug fix actually resolves the issue?▼

Verification involves running tests, reviewing outputs, and confirming the fix addresses the diagnosed root cause before declaring completion. This protocol ensures changes are validated and prevents introducing regressions or shipping incomplete fixes.