codebase-search

When to use

• 

  When you need to find where a specific feature is implemented or how an API is used

• 

  When you are tracing function calls and dependencies to understand the code's impact

• 

  When you are locating the source of a bug or error message across many files

How to use

1. 1

   Choose a strategy: 'Semantic' for concepts, 'Grep' for exact text, or 'Glob' for file types

2. 2

   Start with a broad search to identify relevant directories, then narrow down to specific files

3. 3

   Use advanced techniques to trace data flow or understand a feature end-to-end (from route to DB)

4. 4

   Perform impact analysis before making changes by finding all callsites and related tests

Example conversation

case

You

Where is the user authentication logic and which files depend on it?

Agent

I've used semantic search to locate the 'auth/' directory and grep to find the 'verify_token' function. I've also identified 12 files that import this module, giving you a clear map of the authentication dependencies.

FAQ

Q：When should I use semantic search versus grep?

Q：Can I search for specific file types?

Q：How does this help with debugging?

Q：Does it support complex regex patterns?