Codebase intelligence for AI and humans: code health scores, auto-generated docs, git analytics, dead code detection, and architectural decisions via MCP.
Python aicode-complexitycode-healthcode-intelligencecode-qualitydead-codedeveloper-toolsdocumentationgit-analyticsmcpopen-sourcepythonrefactoringstatic-analysistechnical-debt
description: Diagnose the Repowise setup — install, API keys, index/store drift — and optionally repair it. allowed-tools: Bash(repowise doctor:*), Read
Repowise Doctor
Check that Repowise is healthy: the install, configured provider / API keys, and whether the index and stores are consistent with the repo.
Steps
- Run
repowise doctor. - Summarize what passed and what didn't. For each problem, give the concrete fix
(set an env var, run
/repowise:update, re-run/repowise:init, etc.).
Flags from $ARGUMENTS
- "repair" / "fix" →
repowise doctor --repair(attempts to fix detected mismatches). Tell the user what it changed. - "workspace" →
repowise doctor --workspace(check every repo in the workspace);--no-workspaceto force single-repo. - a path →
repowise doctor <path>
Common findings
- repowise not installed / not on PATH → suggest
pip install repowise(orpython -m pip install repowiseon Windows), then/repowise:init. - No API key for the configured provider → show the exact
exportfor the provider in.repowise/config.yaml. This is not fatal forinit, which falls back to the template wiki. Only an explicitly named--providererrors out. - Index drift (HEAD ahead of last sync) → run
/repowise:update. - Missing embeddings / store drift →
/repowise:reindex.