From solon-core
Debug systematically with root cause analysis before fixes. Use for bugs, test failures, unexpected behavior, performance issues.
How this skill is triggered — by the user, by Claude, or both
Slash command
/solon-core:debugThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Structured debugging framework. NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
Structured debugging framework. NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
/sl:debug <error or issue description>
Never guess. Never "quick fix". Always trace root cause with evidence.
Red flags — stop and follow process:
Gather all available evidence:
sl lsp diagnostics <file> for type/compile errors/sl:scout to find relevant filessl ast search to find related code patternsgit log --oneline -10 for recent changes that may have introduced the issueDocument: what fails, when, where, error messages verbatim.
Based on collected evidence, form 2-3 ranked hypotheses:
## Hypotheses
1. **[Most likely]** Description — supported by evidence X, Y
2. **[Possible]** Description — supported by evidence Z
3. **[Unlikely]** Description — would explain symptom A but not B
For each hypothesis (most likely first):
sl lsp goto-definition and sl lsp references to follow the call chainMove to next hypothesis only after current one is conclusively rejected.
Before declaring root cause found:
sl lsp diagnostics confirms the locationNO COMPLETION CLAIMS WITHOUT FRESH EVIDENCE.
Save to reports path: debug-{date}-{slug}.md
# Debug Report: {issue}
**Date:** {date}
**Status:** Root cause identified / Still investigating
**Severity:** Critical / High / Medium / Low
## Symptoms
{what was observed, error messages}
## Evidence Chain
1. {evidence 1} → leads to
2. {evidence 2} → leads to
3. {root cause}
## Root Cause
{precise explanation with file:line references}
## Recommended Fix
{specific fix steps — do NOT implement, just recommend}
## Verification Plan
{how to confirm the fix works}
4-phase: Investigate → Pattern Analysis → Hypothesis Testing → Verification. Best for: unknown bugs, intermittent failures.
Trace backward through call stack using sl lsp goto-definition and sl lsp references.
Best for: errors with clear stack traces.
Validate at every layer after finding suspected cause. Best for: security issues, data corruption.
sl lsp and sl ast commands as primary investigation tools/sl:fix for implementationUse naming pattern from ## Naming section in hook context. Fall back to plans/reports/debug-{date}-{slug}.md.
npx claudepluginhub huynhhoangphuc/solon --plugin solon-coreGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.