Code Visualization — Codebase Atlas

Produce one self-contained HTML file with tabs. Five tabs are generated by bundled scripts (deterministic analysis — inventory, dependencies, hotspots, coverage, LLM ops); the rest you write yourself after reading the code (judgment analysis). The assembler stitches everything together.

The atlas exists to help a reader catch errors and poor design, not to admire the code. Every tab should either orient the reader or surface something checkable: cycles, hotspots, smeared concerns, unenforced invariants, intent-vs-implementation gaps.

Workflow

Let SKILL=/path/to/this/skill and pick a scratch working dir for intermediate files (any temp location works, e.g. WORK=<temp>/atlas-<repo>), with TABS=$WORK/tabs. Commands below are POSIX-shell shaped; adapt paths/variables to your shell (PowerShell: $env:TEMP, ${SKILL}).

1. Locate the repo

The target is a local directory (uploaded, cloned, or already present). If the user gives a GitHub URL, clone it (git clone --depth 200 <url> — some history is needed for hotspots; use full clone if small). If there's no git history, hotspots will be skipped automatically — that's fine.

2. Run the automated analyzers