debug-production

Investigate a production bug in a fixed order. Find the failing issue, read its stack and first-seen release, pull the logs and trace around the first event, check who is affected, state what is unknown, fix it, then check that new events stop. Use when someone asks why something broke in production, why checkout or login fails, what an error or stack trace means, or to debug a crash, exception, 500 error, or error spike. Reads LogBrew through its MCP server or the logbrew CLI, and works from a pasted stack trace and logs when no tool is connected.

License

MIT