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
| Parameter | Type | Default | Description |
|---|---|---|---|
repo | string | default repo | Repository alias, path, or ID. Omit for the default repo. Pass "all" for a workspace-level overview. |
include | string[] | — | Opt-in extras. "content" returns the full overview essay in content_md instead of the compact summary section. "outline" expands the stored page tree one rung deeper (modules under their layer). |
Returns
| Field | Description |
|---|---|
title | Repo name |
content_md | Full markdown overview (architecture summary, tech stack, data flow, areas to focus on first). content_hint accompanies it when trimmed to the summary section, pointing at include=["content"] for the full essay |
code_health | Always present. The repo's rolled-up health scores |
key_modules | Top module pages, each with name, path, description |
entry_points | File paths for the natural entry points (test fixtures excluded) |
git_health | files_git_attributed, hotspot_count, avg_bus_factor, files_with_bus_factor_1, churn_trend, top_churn_modules |
knowledge_map | top_owners: top 3 contributors by files owned, with files_owned and percentage |
community_summary | Top 10 architectural communities by size, each with id, label, size |
outline | The stored page tree, top rung by default (one level deeper with include=["outline"]). outline_hint explains how to read section and descendants |
architecture | (when available) architecture summary for the repo |
key_decisions | (when available) governing architectural decision records |
reading_order | (when available) canonical onboarding sequence of page_ids. reading_order_hint explains how to walk it |
guided_tour | (when available) the topology-driven, page-by-page walk derived from the import graph (entry points first, then inward, infra last). guided_tour_hint accompanies it |
tool_guide | Always present. Composition recipes for which tool to call next |
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". top_ownersis capped at the top 3 contributors by files owned. It's "who do I ask" orientation, not a per-file ownership signal; for that useget_riskorget_context(include=["ownership"]).- Module pages are capped at 8 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 small, curated set of 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: it 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.