error-debugger_skill

Overview

This skill provides context-aware error debugging that searches past solutions, analyzes error messages and stack traces, and returns immediate, actionable fixes with code examples. It automatically creates regression tests for verified fixes and saves solutions to memory so the skill gets smarter over time. Use it to reduce debugging friction and recall previously effective remedies across your projects.

How this skill works

When an error is reported or a trigger phrase is used, the skill parses the error type, message, stack trace, file, and surrounding context. It searches past saved procedures for fuzzy matches, applies known error patterns, and—if needed—performs external searches as a fallback. The skill returns a clear cause explanation, a minimal code fix with before/after snippets, prevention tips, and an option to generate regression tests and save the solution for future reuse.

When to use it

• You paste a stack trace or error message (TypeError, ECONNREFUSED, CORS, 404, 500, etc.).
• You say: "debug this", "fix this error", or "why is this failing".
• A recurring bug appears and you want a tested, reusable fix.
• You want a regression test created automatically after a fix.
• You need a quick code example showing how to avoid the same failure.

Best practices

• Provide the full error message and nearby code or stack trace for accurate diagnosis.
• Confirm applied fixes locally before telling the skill to save the solution to memory.
• Tag saved solutions with language/framework and context to improve future matching.
• Let the skill generate regression tests and run them in CI to prevent regressions.
• If an external search is required, allow the skill to try at least three approaches before requesting more info.

Example use cases

• Frontend React: Fixing "Cannot read property 'map' of undefined" by adding optional chaining and default arrays.
• Backend API: Resolving ECONNREFUSED by checking service health and port configuration with example retry logic.
• CORS Troubleshooting: Suggesting precise server header changes and a minimal repro to validate.
• HTTP Errors: Diagnosing 404/500 with route checks and server-log extraction guidance.
• Automation: Creating a regression test that fails before the fix and passes afterward, and saving the procedure for reuse.