repowiseget_overview
Architecture summary, module map, entry points, ownership, hotspots, and community structure for an entire repository — the first call your agent should make on any unfamiliar codebase.
The opening move on any new codebase. One call returns a structured architecture summary, the top modules, the natural entry points, git health signals, ownership map, and the major architectural communities.
When to call
- First, before the agent reads any source.
- Workspace orientation — pass
repo="all"to get cross-repo topology and contract links. - Architecture review — re-call before proposing structural changes to refresh hotspot and ownership context.
Parameters
Prop
Type
Returns
| Field | Description |
|---|---|
title | Repo name |
content_md | Full markdown overview (architecture summary, tech stack, data flow, areas to focus on first) |
key_modules | Top module pages — each with name, path, description |
entry_points | File paths for the natural entry points (test fixtures excluded) |
git_health | hotspot_count, avg_bus_factor, churn_trend, top_churn_modules |
knowledge_map | top_owners (with file ownership %), knowledge_silos (files >80% owned by one person, boilerplate excluded) |
community_summary | Top 10 architectural communities by size, with cohesion scores |
workspace | (workspace mode only) root, default repo hint, cross-repo topology, contract links |
Example
get_overview() # default repo
get_overview(repo="frontend") # specific repo in a workspace
get_overview(repo="all") # workspace-level viewThings worth knowing
- Churn trend is computed from a 30-day vs 60-day commit-rate
ratio: above 1.5× is
"increasing", below 0.5× is"decreasing", otherwise"stable". - Knowledge silos filter out boilerplate (migrations,
__init__.py,conftest.py, lock files) so the list reflects real bus-factor risk. - Module pages are capped at 20 and community summaries at 10 to keep the response within the MCP token budget.
- In workspace mode,
repo="all"returns total repos, files, and symbols plus a per-repo dependency graph and contract links between services.
If the agent calls get_overview and immediately follows up with
Grep or Read, your MCP server probably isn't connected — check
.mcp.json and run repowise doctor.
MCP tools — overview
The seven MCP tools repowise exposes to Claude Code and any MCP-compatible AI agent. Task-shaped, batched, and built to collapse long tool-call chains into one round-trip.
get_answer
One-call RAG synthesis over the wiki — retrieves, gates on confidence, and returns a cited 2–5 sentence answer with fallback file targets. The first tool to call on any code question.