basemind-code-search

# basemind-code-search — navigate code without reading it basemind pre-indexes the repo into a tree-sitter code map across 300+ languages. Structural questions — where a symbol lives, what calls it, what shape a file has — resolve from the index in milliseconds and return **paths, line numbers, and signatures, not file bodies**. That is a fraction of the tokens of reading source, so it is the default, not an optimization. **basemind first, grep/read fallback.** If a question is about _where_, _what calls_, _what shape_, or _what implements_, a basemind tool answers it cheaper than `grep`/`rg` or opening files. Drop to raw shell only when no tool covers the question. ## The discipline - **`outline` a file before you open it.** A 1000-line file becomes a 30-line table of contents. Read the actual source only once you have the exact span, then read _that range_, not the file. - **`search_symbols` instead of `grep` for a definition.** It matches indexed symbol names and returns `path:line`, skipping the comment/string/test-name noise grep drowns you in. - **`find_references` / `find_callers` instead of grepping call sites.** Indexed call edges, not text matches. - **`workspace_grep` instead of shelling out to ripgrep** when you genuinely need regex over content — it runs over the in-RAM index and returns capped, structured hits. - **Do not re-read a file basemind already mapped.** If the outline answered the question, stop. - **`rescan` after you edit code**, not a se...