Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From aura-frog
Guides four-phase debugging: investigate errors, analyze differences, hypothesize root causes, fix at source. For bugs, crashes, test/build failures.
npx claudepluginhub nguyenthienthanh/aura-frog --plugin aura-frogHow this skill is triggered — by the user, by Claude, or both
Slash command
/aura-frog:debuggingsonnetThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Systematic debugging framework. Find root cause BEFORE fixing.
Enforces systematic root cause investigation for bugs, test failures, and unexpected behavior through four phases: investigation, pattern analysis, hypothesis testing, and implementation.
Provides four-phase debugging framework prioritizing root cause investigation before fixes. Use for bugs, test failures, unexpected behavior, performance issues, build failures.
Enforces systematic root cause analysis before fixes for bugs, test failures, unexpected behavior, performance issues, and build failures.
Share bugs, ideas, or general feedback.
Systematic debugging framework. Find root cause BEFORE fixing.
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
Random fixes waste time and create new bugs.
git diff, git logWhen error is deep in call stack:
1. Start at error location
2. Trace backward: where did bad data come from?
3. Continue tracing until source found
4. Fix at SOURCE, not symptom
Iron Law: NO COMPLETION CLAIMS WITHOUT FRESH VERIFICATION
# Run verification
npm test # or yarn test, pytest, etc.
# Check output
# THEN claim result
Wrong: "Should work now" Right: "Tests pass: [paste output]"
All mean: Return to Phase 1.
Bug found
→ Phase 1: Read error, reproduce, check changes
→ Phase 2: Find working example, compare
→ Phase 3: Form hypothesis, test minimally
→ Phase 4: Write test, fix, verify
Deep stack error?
→ Trace backward to source
→ Fix at source, not symptom
About to claim fixed?
→ Run verification command
→ Read output
→ THEN claim result
For detailed techniques, see:
references/systematic-debugging.md - Full four-phase detailsreferences/root-cause-tracing.md - Call stack tracingreferences/verification.md - Verification protocols