belentani7 Explore
Use the codebase_search tool to explore a codebase, this saves time and tokens.
When To Use
- Broad questions like "how does this work?" or "where is X implemented?" in code you haven't mapped yet.
- You need entry points, data flow, or ownership of a behavior.
- Keyword grep is likely to miss the relevant files.
Skip it when you already know the file to read or the exact string to grep for.
Steps
- Translate the user question into a tight natural language question, or description of the functionality you're looking for.
- Run 2-3 instances of the
codebase_searchtool against the repo root, for each use a different search_string so you can explore the codebase from multiple angles - Read the returned files/sections.
- Summarize the flow with concrete file paths.
Query Template
"Find the entry points and data flow for . Include router/handlers, config, and tests."