Reindex

by oryf60f9ecee417No licenseListed Oct 8, 2026Updated Oct 8, 2026

Refresh or rebuild the bundled Lumen index for the current project, preferring MCP-driven refreshes and using the CLI only for an explicit clean rebuild.

Instructions onlyAI & Agents
AI-generated overview

Refreshes or rebuilds the bundled Lumen project index via MCP tools, with CLI commands for clean rebuilds.

What it does
This skill guides an agent through refreshing or rebuilding the Lumen index for the current project. It first checks index status, then triggers an automatic refresh through a broad semantic search call, and only falls back to shell commands when the user explicitly requests a clean rebuild. It finishes by reporting index details such as vector precision, unique vectors, deduplication ratio, and database size.
When to use it
Use it when a project's Lumen index is stale, missing, or needs seeding before search. It is also intended for cases where the user explicitly asks for a clean rebuild or wants to reclaim disk space from unused indexes.
Requirements
Requires the Lumen MCP tools (index_status, semantic_search) and, for clean rebuilds, the Lumen CLI available in a shell. No scripts are bundled; instructions only.

Lumen Reindex

Refresh or rebuild the bundled Lumen index for the current project.

Steps

  1. Call the Lumen index_status tool for the current working directory so you can report the current state before making changes.
  2. If the user wants the index refreshed or seeded, call the Lumen semantic_search tool with a broad natural-language query and set path or cwd to the current working directory. The search tool refreshes stale or missing indexes automatically.
  3. If the user explicitly asks for a clean rebuild, explain the options and run one via the shell:
    • lumen index --force . — reprocesses every file for the current project without wiping other worktrees or their shared vectors. Prefer this.
    • lumen clean --days 0 && lumen index . — deletes every cached index not held by an active indexer lock before rebuilding; locked collections are skipped and counted in the summary. Use only when the user asks for a full wipe.
    • lumen clean — removes indexes for projects that no longer exist or have not been used in 30 days. Use to reclaim disk space, not to rebuild the current project.
  4. After the refresh or rebuild, report the new index status, including vector precision, unique vectors, shared references, deduplication ratio, database bytes, and reclaimable bytes when available.

Source and attribution

Source:ory/lumeninskills/reindexat commitf60f9ec

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal