repowiseIndexing — init, update, reindex
The three commands that build and maintain repowise's intelligence layers. init parses everything from scratch, update is incremental on each commit, reindex rebuilds the vector store without re-running the LLM.
repowise init
Generate the wiki for a codebase. Runs full AST parsing, graph analysis, git history indexing, dead-code detection, and (by default) LLM page generation.
repowise init [PATH] [OPTIONS]Prop
Type
repowise init # current dir
repowise init /path/to/repo --provider anthropic
repowise init -x vendor/ -x 'src/generated/**' # multiple excludes
repowise init --index-only # no LLM cost
repowise init --test-run # 10 files, smoke testFirst run takes ~25 minutes for a 3,000-file codebase. init is
idempotent — re-running picks up where it left off unless you pass
--force.
repowise update
Incremental update for files changed since the last sync. Detects
changed files via git diff, re-parses them, rebuilds the affected
slice of the dependency graph, and regenerates the affected pages.
repowise update [PATH] [OPTIONS]Prop
Type
repowise update # incremental from current HEAD
repowise update --since main # diff against main
repowise update --workspace # all stale repos
repowise update --repo backend # one workspace repo
repowise update --dry-run # see what would regenerateA typical single-commit update touches 3–10 pages in under 30 seconds.
repowise reindex
Rebuild the vector search index from existing wiki pages. No LLM calls — only embedding API calls. Fast and cheap. Use when you switch embedders or suspect FTS/vector drift.
repowise reindex [PATH] [OPTIONS]Prop
Type
repowise reindex
repowise reindex --embedder openai --batch-size 50