Debug

When you hit a bug during manual testing and need to figure out what's happening without burning your main context window, this spawns parallel tasks to investigate logs, database state, and git history. It reads recent application logs for errors, queries SQLite databases for stuck states, and checks what changed in your git history. The output is a structured debug report with evidence, root cause analysis, and next steps. Nice for those moments when something breaks and you need to methodically trace through logs and recent commits without cluttering up your implementation context. Won't help with browser console errors or MCP internals, but it handles the server side investigation work competently.