Systematic debugging with root cause investigation. NO fixes without understanding cause first.
/plugin marketplace add nguyenthienthanh/aura-frog/plugin install aura-frog@aurafrogThis skill is limited to using the following tools:
references/root-cause-tracing.mdreferences/systematic-debugging.mdreferences/verification.mdSystematic 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 protocolsVersion: 2.0.0
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in command", or needs guidance on slash command structure, YAML frontmatter fields, dynamic arguments, bash execution in commands, user interaction patterns, or command development best practices for Claude Code.
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development best practices for Claude Code plugins.
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.