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:

Git State:

• Check current branch, recent commits, uncommitted changes
• Similar to how commit and describe_pr commands work

Service Status:

• Check if services are running with ps aux | grep <service>
• Check for relevant log files in the project

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:

Task 1 - Check Recent Logs:
Find and analyze any relevant log files for errors:
1. Look for log files in the project directory
2. Search for errors, warnings, or issues around the problem timeframe
3. Look for stack traces or repeated errors
Return: Key errors/warnings with timestamps

Task 2 - Git and File State:
Understand what changed recently:
1. Check git status and current branch
2. Look at recent commits: git log --oneline -10
3. Check uncommitted changes: git diff
4. Verify expected files exist
5. Look for any file permission issues
Return: Git state and any file issues

Step 3: Present Findings

Based on the investigation, present a focused debug report:

## Debug Report

### What's Wrong
[Clear statement of the issue based on evidence]

### Evidence Found

**From Logs**:
- [Error/warning with timestamp]
- [Pattern or repeated issue]

**From Git/Files**:
- [Recent changes that might be related]
- [File state issues]

### Root Cause
[Most likely explanation based on evidence]

### Next Steps

1. **Try This First**:
   ```bash
   [Specific command or action]

2. If That Doesn't Work:
   • Check for relevant service logs
   • Restart services if applicable
   • Check browser console for frontend errors

Can't Access?

Some issues might be outside my reach:

• Browser console errors (F12 in browser)
• External service internal state
• System-level issues

Would you like me to investigate something specific further?

## 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, external services) are outside reach
- **No file editing** - Pure investigation only

## Quick Reference

**Git State**:
```bash
git status
git log --oneline -10
git diff

Service Check:

ps aux | grep <service>

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 or git state.