/reindex
Rebuild the Repowise vector store by re-embedding all wiki pages. No LLM calls — only embedding API calls.
> /plugin marketplace add repowise-dev/repowise > /plugin install repowise@repowise
How it fires
How this command gets triggered: by you, by Claude, or both.
- Fires itselfClaude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/reindex
Context preview
What this command does when you run it.
Rebuild the Repowise vector store by re-embedding all wiki pages. No LLM calls — only embedding API calls.
Command definition
reindex.mddescription: Rebuild the Repowise vector store by re-embedding all wiki pages. No LLM calls — only embedding API calls. allowed-tools: Bash, Read, AskFollowupQuestion
Repowise Reindex
Rebuild the vector store (embeddings) without regenerating documentation.
This is useful when:
- You switched embedding providers
- The LanceDB vector data got corrupted
- You want to refresh search quality after adding new wiki pages
Steps
1. Check if `.repowise/` exists. If not: "This repo isn't indexed yet. Run `/repowise:init` first."
2. Run: `repowise reindex`
This re-embeds all existing wiki pages into LanceDB. No LLM generation calls — only embedding API calls. Fast and cheap.
Available flags
- `--embedder gemini|openai|auto` — embedding provider (default: auto-detect from env vars)
- `--batch-size N` — pages per embedding batch (default: 20)
Requirements
Requires either `GEMINI_API_KEY`/`GOOGLE_API_KEY` or `OPENAI_API_KEY` to be set. The mock embedder is not accepted for reindexing. If neither key is available, ask the user to set one before proceeding.
Handling $ARGUMENTS
If $ARGUMENTS contains "full" or "from-scratch", confirm with the user: "This will regenerate ALL documentation from scratch, not just re-embed. It will take as long as the initial indexing and cost API tokens. Are you sure?" If yes: `repowise init --force`
Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.
Repo: repowise-dev/repowise
Other commands on repowise.
- /coverage
Ingest or inspect test-coverage reports — LCOV, Cobertura/Clover, or coverage.py .coverage (builds the per-test map when contexts are present).
Open command - /dead-code
Report unreachable files, unused exports, and zombie packages, tiered by confidence.
Open command - /decision
Work with architectural decisions — list, inspect health, add, or confirm auto-proposed decisions.
Open command - /doctor
Diagnose the Repowise setup — install, API keys, index/store drift — and optionally repair it.
Open command - /health
Show Repowise code-health — KPIs, lowest-scoring files, refactoring targets, trends, or per-file markers.
Open command - /impacted-tests
Print the tests whose coverage intersects a change's changed lines — for a commit, base..head range, or staged diff.
Open command

