ridgelisted

# ridge — Codebase Architecture Analysis Ridge is an MCP server that scans codebases (Go, TypeScript, Python, Markdown), builds an architecture graph (nodes + edges), and answers structural questions about the result. This skill teaches when to call which of the 19 tools so you don't pick `arch_scan` for a question that `arch_blast_radius` answers better. ## How to read this skill When the user asks an architecture question, find the matching row in **Tool selection** below, call that tool, and present the answer. Most questions need one tool. A few ("show me a diagram of the current state and what changed since last week") need two. For repeat scans of the same repo, register it first with `arch_registry_add` (gives an alias) so subsequent calls pass `repo: "alias"` instead of an absolute path. ## Tool selection | User intent | Tool | Notes | |---|---|---| | Full overview of a repo | `arch_scan` | Returns nodes, edges, detected topology. Start here when the user hasn't been specific. | | Drill into one subdirectory | `arch_focus` | Same shape as scan, scoped to one path. Use when "just the API service" or "only show internal/handlers". | | Internal vs external vs infrastructure deps | `arch_dependencies` | Returns three categorized lists. Use for "what does this depend on", "what external services does it call". | | What gets affected if X changes | `arch_blast_radius` | Pass the node ID; returns downstream-impacted nodes. Use for "what breaks if I refactor module Y",