Skill
add-benchmark
Add a new benchmark task to the bench-swe pipeline from a real GitHub bug-fix. The human provides the GitHub issue or PR URL; the agent handles extraction,…
Development
Skill
/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.
Install
$ npx -y skills add ory/lumen --skill reindex --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/reindex
Context preview
The summary Claude sees to decide when to auto-load this skill.
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.
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.
Ships withlumen
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.
Get the whole plugin
Stats
290
Stars
32
Forks
Maintained
Maintenance
Go
Language
1mo ago
Last commit
6mo ago
Created
Repo: ory/lumen