/reindex
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.
Claude Code
$ npx -y skills add ory/lumen --skill reindex --agent claude-code
Codex
$ npx skills add ory/lumen --skill reindex -a codex -y
Cursor
$ npx skills add ory/lumen --skill reindex -a cursor -y
Gemini CLI
$ npx skills add ory/lumen --skill reindex -a gemini-cli -y
GitHub Copilot
$ npx skills add ory/lumen --skill reindex -a github-copilot -y
OpenCode
$ npx skills add ory/lumen --skill reindex -a opencode -y
Windsurf
$ npx skills add ory/lumen --skill reindex -a windsurf -y
SKILL.md
reindex.SKILL.mdname: reindex
description: 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.
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.
Read more
name: reindex description: 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.
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.
Save 30% token costs when using Claude Code, Codex, OpenCode for free - with open source, local semantic search. Works for small and large codebases and monorepos! Enterprise-ready and fully compliant via Ollama and SQLite-vec.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about reindex.
- Which coding agents can use reindex?
- reindex installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

