codemap
Skill15 starsChanged 8 months agoApache-2.0View on GitHub
Hybrid vector+BM25 code search, symbol lookup, dependency analysis, PageRank importance scoring, coupling metrics, and circular dependency detection via the codemap CLI. Use when the user asks to search code, find symbols, analyze dependencies, find dependents, check coupling, view PageRank importance, detect circular dependencies, index a project, get file summaries, or explore architecture health. Wraps the @ulpi/codemap CLI (not MCP tools).
- Installs packages
16 other projects use a version of this.
Adopted by
Most recently taken up by
- thistleknot/skillstheir own version, first seen Nov 8, 2026
- openyida/openyidatheir own version, first seen Nov 3, 2026
- hmjBill/skillstheir own version, first seen Oct 29, 2026
- jellydn/my-ai-toolstheir own version, first seen Oct 18, 2026
- mike22890/opencode-skills-entheir own version, first seen Oct 15, 2026
- Asixa/codemap-skilltheir own version, first seen Oct 11, 2026
Used with
Projects with it also use clonedeps and simplify.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
mike22890Skillclonedeps
将项目依赖的第三方库源码克隆到本地,便于深入阅读和调试。当需要查看库的实现细节、阅读源码、调试第三方依赖、理解 SDK/framework 内部机制、查看 node_modules 之外的原始代码、分析开源库架构、学习他人代码、查看依赖的 TypeScript 类型定义时使用。
Also in 4 projects that use this
Hugging FaceSkillsimplify
Refactor code after tests pass. The "Refactor" phase of Red-Green-Refactor.
Also in 4 projects that use this
Other versions16 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 16
- JordanCoin/codemap★ 710same name
- akitaonrails/my-skills★ 283same name
- openyida/openyida★ 231same name
- jellydn/my-ai-tools★ 127same name
- lglucas/ai-dev-operating-system★ 12same name
- Asixa/codemap-skill★ 8same name
- beadnall/codemap★ 8same name
- shalomb/agent-skills★ 3same name
- htdxd/codemap-skill★ 2same name
- arkan/skills★ 1same name
6 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository63 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- agent-browserSkill
- ast-grepSkill
- branch-review-before-prSkill
- browse-qaSkill
- browser-useSkill
- browseSkill
- bugfixSkill
- build-dmgSkill
- claude-reviewSkill
- code-simplifySkill
- codex-reviewSkill
- commitSkill
- cost-estimateSkill
- create-prSkill
- find-agentsSkill
- find-bugsSkill
- frontend-design-ui-uxSkill
- git-merge-expertSkill
- git-merge-expert-worktreeSkill
- kiro-reviewSkill
- laravel-filamentSkill
- laravelSkill
- lokeiSkill
- map-project-monorepoSkill
- map-projectSkill
- nextjsSkill
- plan-founder-reviewSkill
- plan-to-task-list-with-dagSkill
- pr-retroSkill
- run-parallel-agents-feature-buildSkill
- run-parallel-agents-feature-debugSkill
- rustSkill
- secretsSkill
- startSkill
- update-agent-learningsSkill
- update-claude-learningsSkill
- update-claude-settingsSkill
- update-skill-learningsSkill
- ast-grepSkill
- branch-review-before-prSkill
- codemapSkill
- code-simplifySkill
- commitSkill
- cost-estimateSkill
- create-prSkill
- find-bugsSkill
- frontend-design-ui-uxSkill
- git-merge-expertSkill
- git-merge-expert-worktreeSkill
- map-project-monorepoSkill
- map-projectSkill
- plan-founder-reviewSkill
- plan-to-task-list-with-dagSkill
- pr-retroSkill
- run-parallel-agents-feature-buildSkill
- run-parallel-agents-feature-debugSkill
- startSkill
- update-agent-learningsSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 15 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Before running ANY codemap command, you ABSOLUTELY MUST:
- Very specific: line 15
Run codemap status to check if the project is indexed
- Very specific: line 16
If not indexed, run codemap init + codemap index
- Distinctive: line 26
Before running ANY codemap command, complete this checklist:
- Distinctive: line 34
If not installed, tell the user:
- Distinctive: line 42
Do NOT install anything automatically: Wait for the user to confirm they have installed it before proceeding.
- Very specific: line 165
Fix: Run codemap init + codemap index
- Very specific: line 169
Fix: Run codemap index to re-index (or codemap index --full for a complete rebuild)
- Distinctive: line 173
Fix: Verify the file path is relative to the project root and the file exists
“Common” is measured: kept by at least 6 in 10 of the 15 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<EXTREMELY-IMPORTANT>
Before running ANY codemap command, you **ABSOLUTELY MUST**:- Run
codemap statusto check if the project is indexed - If not indexed, run
codemap init+codemap index - Complete the MANDATORY FIRST RESPONSE PROTOCOL below
Running codemap commands without an index = errors and empty results
</EXTREMELY-IMPORTANT>
codemap: Code Search & Architecture Analysis
MANDATORY FIRST RESPONSE PROTOCOL
Before running ANY codemap command, complete this checklist:
Step 1: Verify installation
codemap --versionIf not installed, tell the user:
codemapCLI is not installed. Install it with:npm install -g @ulpi/codemap
Do NOT install anything automatically. Wait for the user to confirm they have installed it before proceeding.
Step 2: Check index status
codemap statusIf no index exists:
codemap init
codemap indexStep 3: Permissions (optional)
To avoid being prompted on every codemap command, tell the user they can add codemap permissions to .claude/settings.local.json under permissions.allow:
"Bash(codemap:*)",
"Bash(codemap search:*)", "Bash(codemap symbols:*)",
"Bash(codemap index:*)", "Bash(codemap status:*)",
"Bash(codemap deps:*)", "Bash(codemap dependents:*)",
"Bash(codemap rank:*)", "Bash(codemap cycles:*)",
"Bash(codemap summary:*)", "Bash(codemap coupling:*)",
"Bash(codemap graph-stats:*)", "Bash(codemap config:*)",
"Bash(codemap init:*)", "Bash(codemap ignore:*)",
"Bash(codemap watch:*)", "Bash(codemap rebuild-depgraph:*)",
"Bash(codemap read:*)", "Bash(codemap serve:*)",
"Bash(codemap statusline:*)", "Bash(codemap update:*)"Do NOT modify settings files automatically. Show the user the permissions and let them decide whether to add them.
MCP Server (alternative to CLI)
Codemap can also run as an MCP server, giving AI agents direct tool access without Bash:
claude mcp add codemap codemap serveThis exposes tools like mcp__codemap__search_code, mcp__codemap__search_symbols, mcp__codemap__get_file_summary, mcp__codemap__get_dependencies, etc.
CLI vs MCP: The CLI skill (this file) uses Bash commands. MCP gives agents native tool calls. Both work — use whichever your agent setup prefers. The CLI skill works across all agents; MCP requires agent-specific configuration.
Command Reference
| Command | What It Does | Key Flags |
codemap search <query> | Hybrid vector+BM25 code search | -l N, --json |
codemap symbols <query> | Find functions, classes, types by name | -l N, --json |
codemap index | Index project for search | --full |
codemap status | Show index stats | --json |
codemap deps <file> | Outgoing imports (what this file uses) | --json |
codemap dependents <file> | Incoming imports (what uses this file) | --json |
codemap rank [file] | PageRank importance scores | -l N, --json |
codemap cycles | Detect circular dependencies | --json |
codemap summary <file> | File overview with symbols and size | --json |
codemap coupling | Afferent/efferent coupling & instability | --module <path>, -l N, --json |
codemap graph-stats | Aggregate dependency graph statistics | --json |
codemap config list/get/set | Manage configuration | |
codemap init | First-time setup | --provider, --force |
codemap ignore | Generate .codemapignore | --force |
codemap watch | Live index updates on file change | --debounce <ms> |
codemap rebuild-depgraph | Rebuild dep graph from scratch | --json |
codemap read <file> | Read full source of a file (or line range) | --start, --end |
codemap serve | Start MCP server over stdio | |
codemap statusline | Install CodeMap status into Claude Code statusline | |
codemap update | Update codemap to latest version |
When to Use Which Command
| What You Want | Command |
| Find code that does X | codemap search "X" |
| Find function/class named X | codemap symbols "X" |
| What does this file depend on? | codemap deps <file> |
| What depends on this file? | codemap dependents <file> |
| Most important files in the project | codemap rank |
| Circular dependencies? | codemap cycles |
| Overview of a file | codemap summary <file> |
| Architecture health / coupling | codemap coupling |
| Project stats | codemap graph-stats |
Common Workflows
Understand a new codebase
codemap status # Check index health
codemap graph-stats # High-level architecture stats
codemap rank -l 10 # Top 10 most important files
codemap summary <top-file> # Deep dive into each key fileImpact analysis before refactoring
codemap dependents <file> # What depends on this file?
codemap deps <file> # What does this file depend on?
codemap coupling --module <dir> # Coupling metrics for the moduleFind and fix circular dependencies
codemap cycles # Detect all cycles
codemap deps <file-in-cycle> # Understand each file's imports
# Refactor to break the cycleSearch for implementation patterns
codemap search "error handling" # Find code by concept
codemap symbols "handleError" # Find by exact nameFailure Modes
Index not built
Symptom: codemap search returns an error or no results
Fix: Run codemap init + codemap index
Stale index
Symptom: Recently added files or symbols don't appear in results
Fix: Run codemap index to re-index (or codemap index --full for a complete rebuild)
File not found
Symptom: codemap deps <file> or codemap summary <file> returns an error
Fix: Verify the file path is relative to the project root and the file exists
Integration with Other Skills
start— Check index status during session init; prompt indexing if stalefind-bugs— Usecodemap rankandcodemap couplingto prioritize which files to auditplan-to-task-list-with-dag— Usecodemap dependentsfor impact analysis when decomposing taskscode-simplify— Usecodemap cyclesto find circular deps worth refactoring
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

