basemind-scan
/basemind-scan
Buduje lub odświeża indeks basemind przez polecenie scan w CLI, gdy brakuje indeksu albo jest nieaktualny.
- Autor
- goldziher ↗
- Repozytorium
- basemind ↗
- Licencja
- MIT
- Ostatnia zmiana repozytorium
- 23.10.2026
Ocena i bezpieczeństwo
- Pliki w paczce
- 2
- Skrypty
- 0
- Komentarze HTML
- 0
- Adresy URL w SKILL.md
- 1
Brak sygnałów. Repozytorium zmienione 23.10.2026, bez odwołań do wycofanych modeli i API.
MIT, otwarta: można używać i zmieniać, z zachowaniem informacji o autorze.
Co robi i kiedy
Buduje lub odświeża indeks basemind przez polecenie scan w CLI, gdy brakuje indeksu albo jest nieaktualny.
Wyzwalacze z opisu
Oryginalny opis (EN)
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.
Jak działa
- When to use
- How to run
- Notes
Podgląd SKILL.md
---
type: Playbook
title: 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.
x-ai-rulez:
kind: skill
id: basemind-scan
metadata:
name: basemind-scan
license: MIT
metadata:
author: Goldziher
repository: https://github.com/Goldziher/basemind
---
# basemind-scan — build or refresh the index (no MCP server required)
basemind answers code-map questions from an index in a machine-global cache (Linux
`~/.local/share/basemind/`, macOS `~/Library/Application Support/basemind/`; override
`BASEMIND_DATA_HOME`), keyed by workspace. 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:
```sh
basemind scan # full working-tree scan
basemind scan <path> # scope to a path (incremental)
```
Finding the binary (in order of preference):
1. `basemind` on `PATH`.
2. The plugin-managed binary the MCP launcher caches:
`${XDG_CACHE_HOME:-~/.cache}/basemind/bin/<version>/basemind`.
3. A dev build: `cargo build --release` then `./target/release/basemind scan`.
## Notes
- The scan writes the content-addressed blob store + Fjall inverted index into the machine-global
cache (never inside the repo). Seconds for small repos; ~22 s for an ~80k-file TypeScript monorepo.
- The code map holds code only. Markdown, JSON, YAML, TOML, XML, CSV, INI and similar prose/config/data
files go to the document tier instead (chunked, searchable with `memory` mode `documents`; they
never appear in `symbols`, `outline` or `grep`; `files` and `find` list them). Anything that is neither code nor an
extractable document is **skipped**, not counted as a failure. Existing indexes migrate on the
next scan, which also reclaims stale blobs (`cleanup: reclaimed N orphaned blob(s)`).
- 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 `basemind rescan [path…]` (the CLI forwards to the running daemon) or
`admin { mode: "rescan" }` over MCP instead; the lock error exits with code 3.
- **Indexing directories outside the repo** — set `scan.extra_roots` in the repo-root `basemind.toml`
to a list of absolute paths (e.g. a Bazel external repo cache) to index them alongside the repo.
This needs `BASEMIND_ALLOW_EXTRA_ROOTS` in the environment that launches basemind (`1`, or a
`:`-separated list of absolute workspace roots to grant only those): the config file lives inside
the repository, so without that operator opt-in the entries are ignored with a warning. A
filesystem or volume root and credential directories (`.ssh`, `.aws`, `.gnupg`, `/etc`) are
refused either way.
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.
- Credential and key files (`.env*`, `.aws/`, `.ssh/`, `.npmrc`, `*.pem`, `*.key`, ...) are never
indexed. `[scan] floor_allow` opts a class back in (`.env.*` also matches `.env.example`), but a
credential entry needs `BASEMIND_ALLOW_REPO_CREDENTIALS` in the environment that launches
basemind — a repository's own file cannot un-exclude your secrets.
`[languages.<grammar>]` re-maps or disables a misdetected grammar.
- After a successful scan, both the MCP tools and `basemind code …` have a fresh index.
- The CLI shares the exact same machine-global cache 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.
Pliki w paczce (2)
- SKILL.md 4 KB
- index.md 1 KB
Wersje
| Repozytorium | Wynik | Licencja |
|---|---|---|
| Ta strona · goldziher/basemind | 84 | MIT |
| goldziher/basemind | 100 | MIT |
| goldziher/basemind | 100 | MIT |
Migawka bazy z 13.11.2026 · wersja paczki d676c604d6d0 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 84basemind
Porusza się po dużych bazach kodu przez serwer MCP basemind: konspekty, wyszukiwanie symboli, odwołania i historię commitów. - 100basemind-stats
Pokazuje, ile wywołań mapy kodu wykonano w sesji, rozkład narzędzi i szacunkowo zaoszczędzone tokeny. - 95scan-codebase
Skanuje bazę kodu Pythona i buduje strukturalny indeks JSON z grafem importów i metrykami zasięgu zmian, przy odświeżaniu indeksu codemap. - 100bb-index-onboarding
Podłącza indeks projektu do bb, gdy wyniki są puste lub nieaktualne, i konfiguruje dostawcę embeddingów do wyszukiwania. - 100index-status
Sprawdza stan i zdrowie indeksu wyszukiwania grepika oraz prowadzi diagnostykę indeksu. - 100scan-all
Odświeża naraz wszystkie wybrane dokumenty referencyjne projektu, pasujące do dowodów, albo podzbiór wskazany przez --targets=.