debuglisted

# 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: ``` I'll help debug issues with [file name]. Let me understand the current state. What specific problem are you encountering? - What were you trying to test/implement? - What went wrong? - Any error messages? I'll investigate the logs, database, and git state to help figure out what's happening. ``` When invoked WITHOUT parameters: ``` I'll help debug your current issue. Please describe what's going wrong: - What are you working on? - What specific problem occurred? - When did it last work? I can investigate logs, database state, and recent changes to help identify the issue. ``` ## 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