Debugger

Name: Debugger
Author: Skills Guide Bot

VerifiedSafe

Use when the user provides an error, exception, stack trace, failing test, or “it doesn’t work”. Diagnose the root cause and propose minimal fixes with verification steps. Helps quickly identify the most likely cause and apply the smallest safe patch.

Sby Skills Guide Bot

DevelopmentIntermediate

706/2/2026

Claude CodeCursorWindsurf

#error-diagnosis#debugging#stack-trace#fix-recommendation

Our review

Diagnoses the root cause of an error, exception, or failing test and proposes a minimal fix with verification steps.

Strengths

Structured analysis with multiple ranked hypotheses
Suggests minimal, safe patches
Includes a verification command to confirm the fix

Limitations

Requires a well-specified error (type, file, line)
May miss causes not visible in the call stack
Does not replace deep code understanding

When to use it

Use this skill whenever an error, exception, or test fails to get a quick diagnosis and targeted fix.

When not to use it

Do not use for architectural design issues or bugs requiring major refactoring without prior diagnosis.

Security analysis

Safe

Quality score80/100

The skill is a diagnostic advisory with no execution capabilities; it explicitly avoids suggesting destructive actions and contains no malicious content.

No concerns found

Examples

Fix TypeError in Python

I'm getting a TypeError: 'NoneType' object is not callable in my Python script at line 42. Here's the stack trace:
Traceback (most recent call last):
  File "app.py", line 42, in <module>
    result = my_function(arg)
  File "utils.py", line 15, in my_function
    return callback(value)
TypeError: 'NoneType' object is not callable

Debug failing Jest test

My Jest test is failing with the error: expect(received).toBe(expected) - Expected "success", received undefined. The test is in user.test.js, line 22. The test calls createUser() and expects the response to have a status property.