Debug You are tasked with helping debug issues during manual testing or implementation. This command allows you to investigate problems by examining logs, database state, and git history without editing files. Think of this as a way to bootstrap a debugging session without using the primary window's context. Initial Response When invoked WITH a plan/ticket file: When invoked WITHOUT parameters: Environment Information You have access to these key locations and tools: Logs : Application logs (check project specific locations) Common locations: ./logs/ , ~/.local/share/{app}/ , /var/log/ Database (if applicable): SQLite databases can be queried with sqlite3 Check project config for database locations Git State : Check current branch, recent commits, uncommitted changes Similar to how commit and describe pr commands work Service Status : Check running processes: ps aux grep {service} Check listening ports: lsof i :{port} Process Steps Step 1: Understand the Problem After the user describes the issue: 1. Read any provided context (plan or ticket file): Understand what they're implementing/testing Note which phase or step they're on Identify expected vs actual behavior 2. Quick state check : Current git branch and recent commits Any uncommitted changes When the issue started occurring Step 2: Investigate the Issue Spawn parallel Task agents for efficient investigation: Step 3: Present Findings Based on the investigation, present a focused debug report: sql Relevant query and result [Finding from database] bash [Specific command or action] Important Notes Focus on manual testing scenarios This is for debugging during implementation Always require problem description Can't debug without knowing what's wrong Read files completely No limit/offset when reading context Think like commit or describe pr Understand git state and changes Guide back to user Some issues (browser console, MCP internals) are outside reach No file editing Pure investigation only Quick Reference Find Latest Logs : Database Queries (SQLite): Service Check : Git State : Remember: This command helps you investigate without burning the primary window's context. Perfect for when you hit an issue during manual testing and need to dig into logs, database, or git state.