菜单
Build or refresh the basemind index by running `basemind scan` via the CLI. Use this when basemind reports "no index" / "no indexed files", when the MCP server isn't available, or after large changes when the index is stale. Works without the MCP server — it shells the basemind binary directly.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
Navigate codebases and manage caches via the basemind CLI — outlines, symbol search, reference/caller lookups, git history, blame, and diffs. For headless scripting, CI, or when driving the CLI more efficiently than interactive MCP calls. Shares the same index as the MCP server.
Find where code is defined and used without reading files — symbol search, file outlines, references, callers, call graphs, implementations, dependents, and indexed regex over content. Reach for it whenever the user asks "where is X defined", "what calls Y", "what implements Z", "what's the shape of this file", or whenever you're about to grep or open files to learn structure.
Coordinate with other agents working the same repo via basemind's broker — scoped rooms, a per-agent inbox, and two-tier messages. Reach for it whenever you start, finish, or hit a decision while collaborating, or to check whether another agent is already touching the code you're about to change.
Semantic + full-text search over documents and the web via basemind's RAG store — PDFs, Office, HTML, email, images (OCR), plus scraped/crawled web pages, with cross-encoder reranking, keyword and named-entity (NER) filters, and per-document summaries. Reach for it whenever the user asks to "search the docs / PDFs", "find where a topic is discussed", "pull this URL into context", or "what does the documentation say about X".
Explore git history without shelling out to git — recent commits, commits touching a path, per-line and per-symbol blame, structural diffs across revisions, churn ranking, and a symbol's history over time. Reach for it whenever the user asks "what changed recently", "who last touched this", "when did this symbol change", "what's the diff between these revs", or "where's the churn".
Navigate large or unfamiliar codebases via the basemind MCP server — outlines, symbol search, reference/caller lookups, commit history, blame, and diffs without reading source files. Reach for it whenever the user asks "where is X defined", "what calls Y", "what changed recently in Z", or whenever you're about to grep or open many files to find structural information.
| name | basemind-scan |
| description | Build or refresh the basemind index by running `basemind scan` via the CLI. Use this when basemind reports "no index" / "no indexed files", when the MCP server isn't available, or after large changes when the index is stale. Works without the MCP server — it shells the basemind binary directly. |
basemind answers code-map questions from an index under .basemind/. That index is built by
basemind scan. This skill runs the scan via the CLI, so it works even when the MCP server
(basemind serve) is not running — which is exactly the situation when basemind reports
"no index" or "no indexed files", or when MCP tools aren't loaded in the session.
From the repository root:
basemind scan # full working-tree scan
basemind scan <path> # scope to a path (incremental)
Finding the binary (in order of preference):
basemind on PATH.${XDG_CACHE_HOME:-~/.cache}/basemind/bin/<version>/basemind.cargo build --release then ./target/release/basemind scan..basemind/.
Seconds for small repos; ~22 s for an ~80k-file TypeScript monorepo.basemind serve MCP server is already running for this repo it holds the store lock, so a
CLI scan will fail with a lock error. Use the rescan MCP tool (it re-indexes in-process)
instead, or stop the server first.scan.extra_roots in .basemind/basemind.toml
to a list of absolute paths (e.g. a Bazel external repo cache) to index them alongside the repo.
Their files are keyed by absolute path (so results for them are absolute, not repo-relative) and
are (re-)indexed on a full scan only — the live watcher does not track them. Git tools (blame)
don't apply to external files; the code map (symbols / references / outlines) and document search
do.basemind query … have a fresh index..basemind/ index as the MCP server — see the basemind-cli
skill for the full query surface, or basemind-code-search / basemind-git-history /
basemind-documents for the per-capability workflows.