/search
Search the Repowise wiki using natural language, full-text, or symbol search.
> /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
/search
Context preview
What this command does when you run it.
Search the Repowise wiki using natural language, full-text, or symbol search.
Command definition
search.mddescription: Search the Repowise wiki using natural language, full-text, or symbol search.
allowed-tools: Bash, Read
Repowise Search
Search the codebase wiki.
Usage
If $ARGUMENTS is empty, ask: "What are you looking for? You can search with natural language like 'how does authentication work' or 'where is rate limiting handled'."
If $ARGUMENTS is provided, run:
repowise search "$ARGUMENTS"
Search modes
The default mode is `fulltext` (SQLite FTS5). You can specify a mode:
- `--mode fulltext` — fast keyword search (default)
- `--mode semantic` — vector similarity search using embeddings. Requires an embedding provider to be configured. If this fails with an error, suggest running `/repowise:reindex` first.
- `--mode symbol` — fuzzy match on symbol names (functions, classes, variables)
Other flags:
- `--limit N` — max results (default: 10)
Present results
Show results as a clean list with the page title, type, and a brief snippet.
When search comes up empty
Search needs wiki pages, and every indexed repo has them: a keyless run renders the whole wiki from structure. So an empty result is usually not a missing wiki.
- **No pages at all** means the index never finished, or the repo was indexed
with `--mode fast`, which is the one mode that writes no wiki. Suggest `repowise init --yes` (no API key needed), or `repowise init --resume` if a previous run was interrupted.
- **Pages exist but semantic search finds nothing** means the wiki was embedded
with the mock embedder, which keeps full-text search working and leaves semantic search to be built later. Suggest `repowise reindex` with an embedder configured. Full-text and symbol search (`--mode symbol`) work regardless.
Read more
description: Search the Repowise wiki using natural language, full-text, or symbol search. allowed-tools: Bash, Read
Repowise Search
Search the codebase wiki.
Usage
If $ARGUMENTS is empty, ask: "What are you looking for? You can search with natural language like 'how does authentication work' or 'where is rate limiting handled'."
If $ARGUMENTS is provided, run:
repowise search "$ARGUMENTS"
Search modes
The default mode is `fulltext` (SQLite FTS5). You can specify a mode:
- `--mode fulltext` — fast keyword search (default)
- `--mode semantic` — vector similarity search using embeddings. Requires an embedding provider to be configured. If this fails with an error, suggest running `/repowise:reindex` first.
- `--mode symbol` — fuzzy match on symbol names (functions, classes, variables)
Other flags:
- `--limit N` — max results (default: 10)
Present results
Show results as a clean list with the page title, type, and a brief snippet.
When search comes up empty
Search needs wiki pages, and every indexed repo has them: a keyless run renders the whole wiki from structure. So an empty result is usually not a missing wiki.
- **No pages at all** means the index never finished, or the repo was indexed
with `--mode fast`, which is the one mode that writes no wiki. Suggest `repowise init --yes` (no API key needed), or `repowise init --resume` if a previous run was interrupted.
- **Pages exist but semantic search finds nothing** means the wiki was embedded
with the mock embedder, which keeps full-text search working and leaves semantic search to be built later. Suggest `repowise reindex` with an embedder configured. Full-text and symbol search (`--mode symbol`) work regardless.
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

