Structured debugging session — reproduce, isolate, diagnose, and fix. 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.

/debug If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md). Run a structured debugging session to find and fix issues systematically. Usage How It Works What I Need From You Tell me about the problem. Any of these help: Error message or stack trace Steps to reproduce What changed recently Logs or screenshots Expected vs. actual behavior Output If Connectors Available If ~~monitoring is connected: Pull logs, error rates, and metrics around the time of the issue Show recent deploys and config changes that may correlate If ~~source control is connected: Identify recent commits and PRs that touched affected code paths Check if the issue correlates with a specific change If ~~project tracker is connected: Search for related bug reports or known issues Create a ticket for the fix once identified Tips 1. Share error messages exactly — Don't paraphrase. The exact text matters. 2. Mention what changed — Recent deploys, dependency updates, and config changes are top suspects. 3. Include context — "This works in staging but not prod" or "Only affects large payloads" narrows things fast.