القائمة
Map symbols across codebases with codemapper (cm) — tree-sitter AST parsing for call graphs, callers/callees, and entrypoints. Use when exploring unknown code or tracing dependencies.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Renders markdown to self-contained HTML with a custom dark stylesheet and opens in browser. Use when previewing markdown documents, generating styled HTML from README or report files.
Inform the user what is happening — skip passive lookups
Manage version control with Jujutsu (jj) — no staging area, immediate changes, smart rebasing. Use when navigating history, squashing, or pushing to Git remotes.
Programmatic hunk selection for Jujutsu — split, commit, or squash specific hunks without interactive prompts. Use when making partial commits or selective squashes.
Gather facts from the web using evidence-first approach with mandatory citations. Use when researching topics, answering factual questions, or any task requiring web-sourced evidence.
Model minimum-move problems as BFS over a state space. Use when solving bucket pouring puzzles, sliding tiles, or any problem asking for the shortest sequence of moves to reach a goal.
| name | cm |
| description | Map symbols across codebases with codemapper (cm) — tree-sitter AST parsing for call graphs, callers/callees, and entrypoints. Use when exploring unknown code or tracing dependencies. |
| token_cost | 150 |
| related | ["retype","sg","grit"] |
| keywords | ["codemapper","cm","symbol","callers","callees","entrypoints"] |
cm)Maps symbols across your codebase using tree-sitter AST parsing. Everything runs in-memory — no databases. Supports Python, JavaScript/TypeScript, Rust, Java, Go, C, Swift, and Markdown.
Start with project overview, then drill down:
cm stats . # File counts, symbol breakdown, parse timing
cm map . --level 2 --format ai # File structure with symbol counts (compact)
cm query <symbol> # Find functions, classes, methods (fuzzy search)
cm inspect ./path/to/file # Deep dive into one file
Trace the suspected code and its callers:
cm query <suspected_function> --show-body # See the implementation
cm callers <function> # Who calls this?
cm trace <entry_point> <suspected_function> # Call path A → B
cm tests <function> # Find tests for it
Understand impact before changing:
cm callers <function> # Reverse dependencies — who calls this?
cm callees <function> # Forward dependencies — what does it call?
cm tests <function> # Verify coverage exists
cm since main --breaking # Breaking changes vs main
cm entrypoints . # Public exported symbols with no internal callers
cm implements <interface> # All implementations of an interface
cm schema <DataClass> # Field structure for structs, classes, dataclasses
cm diff main # Symbol-level changes vs a commit
cm since v1.0 --breaking # Breaking API changes since a tag
cm blame <symbol> ./file.rs # Who last modified this symbol?
cm history <symbol> # Full evolution of a symbol across commits
--format ai — compact output optimized for LLM context (recommended)--show-body — include actual code, not just signatures--exact — case-sensitive matching (default is fuzzy)--no-cache — always reindexcm stats . to understand project composition--format ai for token-efficient LLM-friendly outputsince, blame, history) require a git repository--no-cache to force reindex after structural changes