Stats
Actions
Tags
From codemunch
Token-efficient codebase overview showing symbol map, file structure, and entry points without reading source files
How this command is triggered — by the user, by Claude, or both
Slash command
/codemunch:explore [path]The summary Claude sees in its command listing — used to decide when to auto-load this command
**First**, run the staleness-gate skill to ensure the index is fresh. Then provide a structured overview using only the codemunch index and directory listing. Do NOT read any source files. If $ARGUMENTS is a file path, show: 1. All symbols in that file (name, kind, line range) 2. Each symbol's signature (from index) 3. Estimated complexity (line count per symbol) 4. Total: "X symbols, Y lines — fetch any with /codemunch:fetch <n>" If $ARGUMENTS is a directory or empty (whole project), show: 1. **File tree** — `find . -type f -name "*.ts" | head -30` (adjust extension per detected languag...
First, run the staleness-gate skill to ensure the index is fresh.
Then provide a structured overview using only the codemunch index and directory listing. Do NOT read any source files.
If $ARGUMENTS is a file path, show:
If $ARGUMENTS is a directory or empty (whole project), show:
find . -type f -name "*.ts" | head -30 (adjust extension per detected language)Always end with a tip on how to dig deeper: "Use /codemunch:find to search symbols, /codemunch:fetch to read one, /codemunch:refs to find usages."
Token target for a full project overview: under 200 tokens.
npx claudepluginhub benmarte/codemunch --plugin codemunch/exploreGuides Socratic exploration of an idea through probing questions, optionally spawns research, then routes outputs to GSD artifacts.
/exploreAnalyzes blockchain addresses, transactions, smart contracts, blocks, and tokens, producing structured markdown reports with balances, histories, holdings, and insights.
/exploreExplores codebase to map structure, detect tech stack, patterns, entry points, and CI/CD setup, producing a structured project overview.
/exploreExplores codebase iteratively by keyword: searches file names, code content, git history; refines results interactively or automatically up to depth N, tracks dependencies, summarizes structure and relations.