Debug

Structured debugging session — reproduce, isolate, diagnose, and fix. Best for error messages, stack traces, staging vs production divergence, or when behavior unexpectedly deviates from expected.

The Debug skill runs a methodical debugging workflow: it helps you reproduce the issue reliably, narrow down the cause through elimination, form a hypothesis, and verify the fix. It's especially useful for elusive bugs that resist casual investigation.

When to use

Trigger with an error message or stack trace, 'this works in staging but not prod', 'something broke after the deploy', or when behavior diverges from expected and the cause isn't obvious.

Examples

Diagnose a stack trace

Paste an error and get a structured diagnosis

Getting this in production: TypeError: Cannot read properties of undefined (reading 'id') at processOrder (/app/orders.js:42)

Staging vs prod divergence

Debug environment-specific issues

This works perfectly in staging but throws a 500 in production. Same code, same data.

Post-deploy regression

Track down what a deploy broke

Something broke after our 3pm deploy. Checkout flow is failing but only for logged-out users.