repowise MCP工具

What repowise builds

repowise runs once, builds everything, then keeps it in sync on every commit.

Install post-commit hook for one repo

repowise hook install

Install for all repos in a workspace

repowise hook install --workspace

Proactive hooks (auto-installed by init — not called manually)

repowise augment # enriches agent tool calls with graph context

Quickstart

pip install repowise

Or install the CLI into an isolated, uv-managed environment:

uv tool install repowise

Configuration

repowise init generates .repowise/config.yaml. Key options:

provider: anthropic               # anthropic | openai | openrouter | gemini | deepseek | ollama | litellm | mock
model: claude-sonnet-4-5
embedding_model: voyage-3
reasoning: auto                   # auto | off | minimal

git:
  co_change_commit_limit: 500
  blame_enabled: true

dead_code:
  enabled: true
  safe_to_delete_threshold: 0.7

maintenance:
  cascade_budget: 30              # max pages fully regenerated per commit
  background_regen_schedule: "0 2 * * *"

reasoning applies to documentation generation. auto preserves provider defaults; explicit off / minimal modes are translated only by providers and models that support them, otherwise repowise fails before making an API call.

Full configuration reference: docs/CONFIG.md

---

WHY: JWT chosen over sessions — API must be stateless for k8s horizontal scaling

DECISION: All external API calls wrapped in CircuitBreaker after payment provider outages

TRADEOFF: Accepted eventual consistency in preferences for write throughput

```

These become structured decision records, queryable by Claude Code via get_why().

CLI reference

```bash

Tool call comparison — a real task

"Add rate limiting to all API endpoints."

Here are those five calls, and what each one actually returns:

User: Implement rate limiting on all API endpoints

Claude Code:
→ get_overview()
  "Express API. Entry points in api/routes/. Middleware in middleware/."

→ get_context(["middleware", "api/routes", "payments"])
  middleware/: existing chain is cors → auth → routes. Owner: @alex.
  api/routes/: 23 route files. No existing rate limiting.
  payments/: Owner @sarah (71%). Decision: all side effects must be idempotent.

→ get_why("rate limiting")
  "No prior decision found. No prior implementation detected."

→ get_risk(["middleware/auth.ts"])
  "47 files import this. Co-changes with all 4 service listeners.
   Risk summary: any interface change here touches 47 dependents."

→ search_codebase("rate limit throttle retry")
  "Found: payments/retry.ts already has RetryQueue class.
   Found: payments/middleware.ts has idempotency key middleware."

Implementing rate-limiting middleware, inserting after cors, before auth.
Will also update tests/middleware.test.ts — detected as historical co-change partner.
Flagging payments/ for @sarah review — hotspot, high ownership concentration.

This is what happens when an AI agent has real codebase intelligence.

---

How it compares

The honest summary:

• vs Google Code Wiki — Google's offering (launched Nov 2025) is cloud-only with no private repo support yet. Gemini-powered docs are strong, but there's no git behavioral intelligence, no dead code detection, no MCP server, and no architectural decisions.
• vs DeepWiki — Cloud-only, closed source (community self-hostable forks exist). Strong docs and Q&A, with a basic 3-tool MCP server. No git analytics, no dead code, no decisions.
• vs Swimm — Swimm's strength is keeping manually-written docs linked to code snippets with staleness detection. No graph, no git behavioral analytics, no dead code, no MCP by default. Enterprise pricing for private hosting.
• vs CodeScene — CodeScene has excellent git intelligence (hotspots, co-changes, ownership, bus factor). No documentation generation, no RAG, no architectural decisions. Closed source, per-author pricing.

repowise is the intersection: CodeScene-level git intelligence + auto-generated documentation + agent-native MCP + architectural decisions + multi-repo workspace intelligence, self-hostable and open source.

---