Run any Skill in Manus with one click

basemind-scan

Stars39

Forks9

UpdatedJuly 2, 2026 at 09:46

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Goldziher

Goldziher/basemind

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

SKILL.md

readonly

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-scan — build or refresh the index (no MCP server required)

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.

When to use

basemind / the statusline reports no index for this repo.
An MCP tool returns "no indexed files" or empty results that should not be empty.
The MCP server isn't running or isn't reachable, and you need the code map.
The index is stale after large changes and you want a full rebuild.

How to run

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.
The plugin-managed binary the MCP launcher caches: ${XDG_CACHE_HOME:-~/.cache}/basemind/bin/<version>/basemind.
A dev build: cargo build --release then ./target/release/basemind scan.

Notes

The scan writes the content-addressed blob store + Fjall inverted index under .basemind/. Seconds for small repos; ~22 s for an ~80k-file TypeScript monorepo.
Files tree-sitter doesn't recognize as code go through the document tier; anything that isn't an extractable document (e.g. an exotic source file) is skipped, not counted as a failure.
If a 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.
Indexing directories outside the repo — set 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.
After a successful scan, both the MCP tools and basemind query … have a fresh index.
The CLI shares the exact same .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.

More from this repository

same repository

basemind-cli

Goldziher/basemind

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.

2026-07-0239

basemind-code-search

Goldziher/basemind

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.

2026-07-0239

basemind-comms

Goldziher/basemind

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.

2026-07-0239

basemind-documents

Goldziher/basemind

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".

2026-07-0239

basemind-git-history

Goldziher/basemind

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".

2026-07-0239

basemind

Goldziher/basemind

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.

2026-07-0239

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-scan — build or refresh the index (no MCP server required)

When to use

basemind / the statusline reports no index for this repo.
An MCP tool returns "no indexed files" or empty results that should not be empty.
The MCP server isn't running or isn't reachable, and you need the code map.
The index is stale after large changes and you want a full rebuild.

How to run

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.
The plugin-managed binary the MCP launcher caches: ${XDG_CACHE_HOME:-~/.cache}/basemind/bin/<version>/basemind.
A dev build: cargo build --release then ./target/release/basemind scan.

Notes

The scan writes the content-addressed blob store + Fjall inverted index under .basemind/. Seconds for small repos; ~22 s for an ~80k-file TypeScript monorepo.
Files tree-sitter doesn't recognize as code go through the document tier; anything that isn't an extractable document (e.g. an exotic source file) is skipped, not counted as a failure.
If a 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.
Indexing directories outside the repo — set 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.
After a successful scan, both the MCP tools and basemind query … have a fresh index.
The CLI shares the exact same .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.