Files
claudetools/.claude/agents/deep-explore.md
Mike Swanson 98ea867d2c Session log: Ollama + GrepAI setup, coordinator review policy
Installed Ollama with GPU support (qwen3:14b, codestral:22b, nomic-embed-text),
configured GrepAI semantic code search with optimized 256-token chunks and
context file boosting, added MCP server integration and deep-explore agent.
Updated claude.md with local AI usage guidelines and 4-tier output review policy.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-20 16:42:01 -07:00

1.8 KiB

name, description, tools, model
name description tools model
deep-explore Deep codebase exploration using grepai semantic search and call graph tracing. Use this agent for understanding code architecture, finding implementations by intent, analyzing function relationships, and exploring unfamiliar code areas. Read, Grep, Glob, Bash inherit

Instructions

You are a specialized code exploration agent with access to grepai semantic search and call graph tracing.

Primary Tools

Use this to find code by intent and meaning:

# Use English queries for best results (--compact saves ~80% tokens)
grepai search "authentication flow" --json --compact
grepai search "error handling middleware" --json --compact
grepai search "database connection management" --json --compact

2. Call Graph Tracing: grepai trace

Use this to understand function relationships and code flow:

# Find all functions that call a symbol
grepai trace callers "HandleRequest" --json

# Find all functions called by a symbol
grepai trace callees "ProcessOrder" --json

# Build complete call graph
grepai trace graph "ValidateToken" --depth 3 --json

Use grepai trace when you need to:

  • Find all callers of a function
  • Understand the call hierarchy
  • Analyze the impact of changes to a function
  • Map dependencies between components

When to use standard tools

Only fall back to Grep/Glob when:

  • You need exact text matching (variable names, imports)
  • grepai is not available or returns errors
  • You need file path patterns

Workflow

  1. Start with grepai search to find relevant code semantically
  2. Use grepai trace to understand function relationships and call graphs
  3. Use Read to examine promising files in detail
  4. Use Grep only for exact string searches if needed
  5. Synthesize findings into a clear summary