error-resolver-workflow-skill

What I do

I diagnose and help resolve errors, exceptions, and stack traces:

• Analyze error messages from various sources (runtime, compilation, tests)
• Parse stack traces to identify root causes
• Provide actionable solutions and fixes
• Handle error screenshots via MCP integration

When to use me

IMPORTANT: This skill is ONLY triggered by EXPLICIT user invocation. I am NOT automatically triggered for general error handling.

Use when user explicitly requests:

• "use error resolver" / "error resolver" / "resolve this error"
• "fix this error" / "fix error" (when explicitly invoking the resolver)
• "diagnose this error" / "diagnose error"
• "analyze this exception" / "analyze error"

Do NOT auto-trigger for:

• General debugging without explicit request
• Automatic error detection during development
• Implicit error handling in other workflows

Steps

Step 1: Identify Error Source

Error Types:

Type	Indicators	Common Sources
Runtime	Exception, Error, crash	Application logs, terminal
Compilation	SyntaxError, TypeError	Build output, IDE
Test	AssertionError, pytest failures	Test runner output
Infrastructure	Connection refused, timeout	Server logs, cloud console
Screenshot	Visual error display	User-provided image

Step 2: Parse Error Information

Extract Key Data:

• Error type/class (e.g., TypeError, NullPointerException)
• Error message (the descriptive text)
• Stack trace (file paths, line numbers, function calls)
• Context (what operation triggered it)
• Environment (OS, runtime version, dependencies)

Step 3: Analyze Root Cause

Analysis Patterns:

Runtime Errors:

• TypeError: X is not a function → Check if variable is correct type
• ReferenceError: X is not defined → Check variable scope/declaration
• NullPointerException → Check for null/undefined values
• IndexError/IndexOutOfBounds → Check array bounds

Compilation Errors:

• Syntax errors → Fix syntax at indicated line
• Type mismatches → Check type annotations
• Missing imports → Add required imports