eddmann ultrathink: Answer this question by first exploring the codebase thoroughly, then providing a well-researched answer with specific references.
Your Question
$ARGUMENTS
Context
- Current directory: !
pwd - Git branch: !
git branch --show-current 2>/dev/null || echo "not a git repo"
Instructions
Phase 1: Understand the Question
Before searching:
- Parse what's being asked - what information is needed?
- Identify likely locations - where might the answer be?
- Plan your search - what patterns, files, or concepts to look for?
Phase 2: Explore Thoroughly
Search the codebase comprehensively:
- Use Explore agents for broad searches
- Read relevant files - don't just grep, read context
- Trace connections - follow the code paths
- Check multiple locations - the answer might be spread across files
- Look at tests - they often document behavior clearly
Spend time here. Read widely. Don't answer until you've explored thoroughly.
Phase 3: Synthesize Answer
Provide a complete answer:
- Answer the question directly - lead with the answer
- Provide evidence - file:line references for claims
- Explain context - why things work this way
- Note related info - things the user might want to know
Output Format
## Answer
[Direct answer to the question]
## Details
[Explanation with file:line references]
## Related
[Optional: related things worth knowing]
Critical Rules
- DO NOT make changes - this is research only
- DO NOT guess - if unsure, say so and explain what you found
- DO include references - file paths and line numbers
- DO explore thoroughly - read before answering