debug-helper

To find the root cause of an error, parse the stack trace to extract the error type, file, and line numbers. This skill analyzes the extracted data to categorize the root cause, such as a type mismatch, logic error, or async problem.

The best way to debug code failures is applying targeted analysis across languages to locate implicated files and recent commits. This approach categorizes the root cause and guides you through a structured, five-step debugging workflow.

To troubleshoot an error message, provide the message to the skill for parsing. It extracts relevant details, categorizes the issue into classes like dependency or environment problems, and proposes targeted code fixes.

Yes, this debugging workflow handles various software errors by categorizing them into type mismatches, logic errors, async problems, dependency issues, environment problems, or data problems to guide the fix.

To fix an error after root-cause identification, follow the structured five-step guided workflow. This process helps locate the exact source, propose specific code edits, and validate the applied fix within your development workflow.

Error analysis should not stop at the failing line because the root cause often lies elsewhere. This skill categorizes the underlying issue and finds related occurrences and recent commits to guide a complete fix.