codebase-anatomylisted

# Codebase Anatomy (codeweb) Build a "biological web" of a system: every atomic part (function, class, method, exported symbol) is a node; calls/imports/inheritance are the edges; each node belongs to a domain; and an **overlap graph** shows where separate parts do the same work — the simplification targets. The goal is not a pretty picture. It is an **evidence-backed restructure plan**: which duplicated logic should collapse into one well-defined system, and who should depend on it. ## When to Use - Restructuring your own codebase and you need to *see* the real dependency web and where it's duplicative before moving code. - Onboarding to a large/legacy system at symbol resolution, not just folder-level. - Reviewing an **external** repo (a plugin, library, or template you found on GitHub) end-to-end before adopting it — what it does, how it's wired, and whether it's worth committing to. - Hunting cross-cutting duplication that file/module tools miss (the same check coded N times in N domains). ## Two Modes - **internal** — analyze the current project; produce a domain map + overlap graph + restructure recommendations. - **external** — `target` is a git URL or `owner/repo`. Clone it **read-only** to a temp dir, map it the same way, and add an **adoption review** (risk, dependencies, architecture verdict, "should you adopt this?"). Auto-detect: a URL or `owner/repo` ⇒ external; a path or `.` ⇒ internal. `--mode` overrides. ## Non-Negotiable Rules - **Never