| name | code-search |
| description | Routes code search requests to semantic, structural, repo-discovery, or text-search workflows. Use when the user wants to find code, inspect repository layout, or search by meaning or syntax. |
Help the assistant choose the right code-search strategy for the task: start with repo discovery when needed, prefer osgrep for semantic search, use ast-grep for structural matching, and fall back to ripgrep for exact text search.
<quick_start>
<default_order>
- If the repo layout is unclear, load
workflows/repo-discovery.md.
- If the user wants "find code by meaning", load
workflows/semantic-search.md.
- If the user wants a structural pattern, load
workflows/structural-search.md.
- If the user wants a literal match, load
workflows/text-search.md.
</default_order>
Default to the `osgrep` CLI for semantic code search. If the repo does not have a usable root index, create or refresh it with `osgrep index` before searching. Confirm availability with `osgrep --help`; if unavailable, fall back to ripgrep-based discovery. Never start the `osgrep mcp` or `osgrep serve` background processes — use the CLI commands directly.
What kind of code search do you want?
- Find code by meaning or concept
- Find code by structure or AST shape
- Get the lay of the land in a repo
- Find exact text or identifier matches
Wait for the answer, then follow the matching workflow.
| Response | Workflow |
|----------|----------|
| 1, "meaning", "semantic", "concept", "osgrep" | `workflows/semantic-search.md` |
| 2, "structure", "ast", "ast-grep", "pattern" | `workflows/structural-search.md` |
| 3, "layout", "overview", "repo", "land" | `workflows/repo-discovery.md` |
| 4, "text", "literal", "identifier", "grep", "ripgrep" | `workflows/text-search.md` |
<reference_index>
references/tool-selection.md - Tool priorities and fallback rules
