Error Resolver

What it does

The Error Resolver is designed to intelligently identify and suggest fixes for common errors across various programming languages and frameworks. It uses a structured, five-step process (Classify, Parse, Match, Analyze, Resolve) to diagnose issues, extract key information from error messages (including stack traces), and provide both immediate fixes and preventative measures. The skill aims to improve the clarity and accuracy of code by addressing errors systematically.

When to use it

• When encountering syntax errors like typos or missing brackets.
• To troubleshoot type-related errors, such as incorrect data types or null/undefined access issues.
• For resolving reference errors caused by undefined variables or scope problems.
• Debugging runtime errors and logic flaws within your code.
• Addressing network connectivity problems (e.g., connection refused, timeouts).

Key capabilities

• Error Classification: Categorizes errors into primary categories like Syntax, Type, Reference, Runtime, Network, Permission, Dependency, Configuration, Database, and Memory.
• Information Extraction: Parses error messages to extract key details such as error codes, file paths, line numbers, function names, variable values, and stack trace depth.
• Pattern Matching: Compares errors against known patterns for language-specific solutions.
• Root Cause Analysis: Uses techniques like the "5 Whys" to determine the underlying cause of an error.
• Solution Generation: Provides both immediate fixes ("Get it working now") and proper, long-term solutions ("The right way to solve it"), along with preventative measures.

Example prompts

• “I’m getting a TypeError: Cannot read property 'name' of undefined. Can you help me resolve this?”
• "Here's my error log: ModuleNotFound: No module named 'requests'. What's causing it?" (Include relevant code if possible)
• "I have an ECONNREFUSED error. What are the most likely causes and how can I fix it?"

Tips & gotchas

• Provide the full error message, including any stack traces available, for best results.
• Share relevant code snippets or file paths to give the skill more context.
• The Error Resolver uses a predefined classification framework; while broad, this may not cover every possible error scenario.