菜单
Use at feature start (or when the map is stale) to map the repo's structure ONCE into docs/codebase-map.md — a token-lean, depth-limited structural map that plan-writer, analyze, and implement-feature reuse instead of re-exploring the tree each phase.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
基于 SOC 职业分类
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/CaioWF/keel --skill codebase-map命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Use when designing the structure of a feature or module (in the plan phase, or when refactoring) to apply language-agnostic engineering principles — Clean Architecture, SOLID, testing strategy, and tactical DDD. Container of guides; each concept is a companion.
Use when implementation is complete, gates pass, and you need to decide how to integrate the work — presents structured options (merge, PR, keep, discard) and handles the chosen workflow, including worktree cleanup. Closes the SDD cycle after review-and-simplify.
Use when PAUSING/ending a session (writes the current state to docs/STATE.md to resume later) or when RESUMING (reads docs/STATE.md and the active spec, recomposes context, and proposes the next step). Maintains continuity across human and agent sessions.
| name | codebase-map |
| description | Use at feature start (or when the map is stale) to map the repo's structure ONCE into docs/codebase-map.md — a token-lean, depth-limited structural map that plan-writer, analyze, and implement-feature reuse instead of re-exploring the tree each phase. |
When: at the start of a non-trivial feature/refactor, before or during plan-writer, in a repo the current session has not already mapped — or when docs/codebase-map.md exists but the structure has drifted (new top-level modules, moved boundaries). Skip on a repo small enough to hold in head, or when a fresh map already exists this session. Companion skill, not a forced chain link.
Template: none — produces a generated artifact, not a filled template.
Output: docs/codebase-map.md — a living artifact. Seed once, then refresh in place; never a per-feature file. Token-lean by design: it is read many times (every downstream phase), so it favors a scannable map over prose.
Steps:
docs/codebase-map.md exists and the structure has not drifted, stop — reuse it. Do not regenerate for cosmetic reasons.node_modules, dist, build, .git, vendored deps, or generated output). Prefer one broad Explore/Glob fan-out over reading whole files — locate structure, don't audit code.naming-conventions/postgres-conventions when the stack-conventions pack is installed).TODO/uncertain rather than inventing.docs/codebase-map.md. Record the commit/date it reflects at the top so drift is detectable later.Next: plan-writer reads docs/codebase-map.md to ground Architecture / File Structure in the real structure; analyze and implement-feature reuse it. Regenerate when the structure drifts, not per feature.