About debug-error
debug-error is a skill for analyzing error messages and suggesting fixes when users request root-cause analysis. It returns plausible causes, concrete remediation steps, and a verification step; it is not intended for feature requests or non-debug planning.
Key features
- 01Analyzes error messages or stack traces
- 02Suggests plausible root causes
- 03Provides concrete remediation steps
- 04Includes a verification step
Use cases
- 01Find the cause of a runtime error
- 02Plan a fix from a stack trace
- 03Verify whether an error fix worked
Install
Copy the command and run it in a terminal.
$
npx skills add https:/After installing, type/debug-errorin Claude Code to confirm it loaded.
Details
From the project READMEDebug Error
Purpose
Analyze an error message and suggest fixes
Routing
- Use when: Use when user shares an error message and asks for root-cause analysis.
- Do not use when: Don't use for feature requests or non-debug planning questions.
- Outputs: Root-cause analysis and concrete remediation steps.
- Success criteria: Provides plausible cause, fix plan, and verification step.
Trigger Examples
Positive
- Use the debug-error skill for this request.
- Help me with debug error.
- Use when user shares an error message and asks for root-cause analysis.
- Debug Error: provide an actionable result.
Negative
- Don't use for feature requests or non-debug planning questions.
- Do not use debug-error for unrelated requests.
- This request is outside debug error scope.
- This is conceptual discussion only; no tool workflow is needed.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| error | string | Yes | The error message or stack trace |
Runtime Prompt
- Current runtime prompt length: 429 characters.
- Runtime prompt is defined directly in
../debug-error.json.
Comments
Markdown supported