codemaplisted

# Codemap Skill You help users understand and map repositories by creating hierarchical codemaps. ## Announce before you start This skill is expensive: it reads the whole tree and spawns one writer agent per directory. On a few-hundred-file repository that is real money and several minutes. It also **writes files into the user's repository**: a `codemap.md` in every mapped directory, `.slim/codemap.json`, and a section in root `AGENTS.md`. So: say what it will cost and what it will write, and get a yes first. Reaching for it unprompted is correct; doing so silently is not. Proposing and running are different acts, and only the first is yours. If the repository is small enough to simply read, read it instead. ## When to Use - User asks to understand/map a repository - User wants codebase documentation - Starting substantial work on an unfamiliar codebase ## Workflow ### Step 1: Check for Existing State **First, check if `.slim/codemap.json` exists in the repo root.** If `.slim/codemap.json` exists: Skip to Step 3 (Detect Changes) - no need to re-initialize. If it does not exist: Continue to Step 2 (Initialize). ### Step 2: Initialize (Only if no state exists) 1. **Analyze the repository structure** - List files, understand directories 2. **Infer patterns** for **core code/config files ONLY** to include: - **Include**: `src/**/*.ts`, `package.json`, etc. - **Exclude (MANDATORY)**: Do NOT include tests, documentation, or translations. - Tests: `**/*.test