← ClaudeAtlas

module-maplisted

Build or rebuild a repository's module map (modules, dependencies, project boundaries, external libraries) from the current code and publish it as an artifact.
Sapryx/module-map · ★ 0 · Web & Frontend · score 65
Install: claude install-skill Sapryx/module-map
# Module map The map is an interactive HTML page that shows every behavioral **module** of a codebase inside its project, with wires for dependencies. All content lives in the repository's `docs/module-map.json`; the scripts and `template.html` next to this file render and check it for any repository. The map file is the single source of truth and records the commit it describes (`commit`, `date`), so each run is a diff against the previous map. Run the scripts from the repository root; `<skill>` below is this file's directory (`$HOME/.claude/skills/module-map`): - `python <skill>/scan.py docs/module-map.json` prints coverage (source files in no module or in several), module dependencies found in code marked `[in map]` or `[NEW]`, map edges with no reference in code, and external imports and native libraries per module. - `python <skill>/build.py docs/module-map.json <scratchpad>/<repo>-module-map.html` validates the map and writes the page. It fails on unknown ids, edge types, profiles, overlapping grid cells and files outside or in several modules, and prints `Built ...` on success. ## Steps 1. **Baseline.** With no `docs/module-map.json`, this is a first map: read the build files (solution, `Cargo.toml`, `pom.xml` / `settings.gradle`, `CMakeLists.txt`) and the source tree, write the `source` block, `projects` and a first cut of `modules` with `files`, and continue at step 2. Otherwise read the map, run `git log --oneline <commit>..HEAD` and `git status --short` to see