To generate, populate, and use a project codemap
68%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./instructions/r3/core/skills/codemap/SKILL.mdWorkspace cartographer. Produces a lightweight, top-level structural map of a project — folder/module layout, key entry points, and ownership — for fast architectural orientation.
Precedence: LSPs > graphify > gitnexus > shell scripts — use the first that is REQUESTED and available.
Keep CODEMAP.md initialized and updated REGARDLESS.
Do not guess or try to figure out those above => if tools existed you would know that already => fallback to scripts and processes below.
IF LSP tools are already in current context: - The Language Server Protocol (LSP) - Use already available tools / capabilities in context - Combine with semantic search / code index tools already available in context - Prefer LSP over Grep/Read for code navigationIF graphify is already REQUESTED in current context:
graphify query/path/explain): MUST USE SKILL graphify/graphify <path>, --update): MUST USE SKILL graphifygraphify update . to keep the graph current (AST-only, no API cost)IF gitnexus is already REQUESTED in current context:
assets/gitnexus-use.mdassets/gitnexus-cli.mdassets/gitnexus-examples.mdnpx gitnexus analyze --force in the workspace root<core_concepts>
CODEMAP.md at the workspace root: markdown headers = workspace-relative path + recursive children count + short (<10 words) description, listing only immediate children file names per directory, 3-4 levels deep..gitignore-excluded files are excluded (the scripts use git ls-files).</core_concepts>
<how_to_generate>
assets/codemap.sh.txtassets/codemap.ps1.txtcodemap.sh [WORKSPACE_ROOT] [MAX_DEPTH]codemap.ps1 -WorkspaceRoot <path> -MaxDepth <n>CODEMAP.md to workspace root.CODEMAP.md and incorporate it into the current task's discovery notes or working context.</how_to_generate>
<how_to_use_output>
large-workspace-handling, which scopes subagents against CODEMAP.md headers.CODEMAP.md — no deltas, no changelogs.</how_to_use_output>
griddynamics/rosetta
ca35acf
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.