codemaplisted

# Codemap Codemap gives you instant architectural context about any codebase. Use it proactively before exploring or modifying code. ## Commands ```bash codemap . # Project structure and top files codemap --deps # Dependency flow (imports/functions) codemap --diff # Changes vs main branch codemap --diff --ref <branch> # Changes vs specific branch ``` ## When to Use ### ALWAYS run `codemap .` when: - Starting any new task or feature - User asks "where is X?" or "what files handle Y?" - User asks about project structure or organization - You need to understand the codebase before making changes - Exploring unfamiliar code ### ALWAYS run `codemap --deps` when: - User asks "how does X work?" or "what uses Y?" - Refactoring or moving code - Need to trace imports or dependencies - Evaluating impact of changes - Finding hub files (most-imported) ### ALWAYS run `codemap --diff` when: - User asks "what changed?" or "what did I modify?" - Reviewing changes before commit - Summarizing work done on a branch - Assessing what might break - Use `--ref <branch>` when comparing against something other than main ## Output Interpretation ### Tree View (`codemap .`) - Shows file structure with language detection - Stars (★) indicate top 5 largest source files - Directories are flattened when empty (e.g., `src/main/java`) ### Dependency Flow (`codemap --deps`) - External dependencies grouped by language - Internal import chains showing h