cmk:codebase-summary
Codebase Summary
Intents
Document the repository structure and key entry points
Update the codebase summary — we reorganized the src/ directory
Map the codebase so new contributors can get oriented quickly
Where does everything live in this project?
References
Read references/codebase-summary-conventions.md for placement rules and references/codebase-summary-template.md for section structure.
Scope
Codebase summary captures repository structure and navigation — how to find things. Architecture rationale belongs in system-design; feature behavior in specs.
Input
Synthesize from: direct codebase exploration (directories, entry points, modules), existing docs (README, package.json, etc.), conversation context, or direct prompts.
Workflow: Create
- Explore the repository to understand layout, entry points, and module boundaries.
- Map into template sections from
references/codebase-summary-template.md. Align to local convention if one exists. - Place at the repository's existing path, or fallback:
docs/codebase-summary.md. - Include local dev commands if discoverable.
Workflow: Iterate
- Read the existing summary in full.
- Explore current codebase to identify what changed.
- Update affected sections in place. Preserve unchanged content.
- Update
Last updateddate.
Output
- Create: complete codebase summary at
docs/codebase-summary.md - Iterate: targeted updates to affected sections only
- Layout matches actual directory structure
- Entry points and dev commands are current and runnable
- No architecture rationale (belongs in system-design)
More from commandosslabs/ai-devkit
cmk:feature-spec
Create or iterate feature specifications. Use whenever someone wants to draft, refine, or update a feature spec — from conversation notes, local docs, external links, or direct prompts. Also triggers for "spec out this feature", "write up the requirements for X", "break this into a spec", or discussions about feature scope, flows, and acceptance criteria.
13cmk:prd
Create or iterate product requirements documents. Use whenever someone wants to draft, refine, or update a PRD — whether from conversation notes, research sessions, user feedback, Notion docs, or direct instructions. Also triggers when users discuss product scope, success criteria, user needs, or say things like "save this as requirements" or "let's define what we're building".
12cmk:rule
Codify engineering standards into docs/rules/. Use whenever someone wants to create, update, or promote knowledge into enforceable coding rules and conventions that agents follow during development. Also triggers for "add a rule that...", "make this a standard", "promote this learning to a rule", "update our coding conventions", or "what are our engineering rules".
8cmk:learn
Extract and record non-obvious learnings, gotchas, and valuable knowledge from any input — conversations, research sessions, debugging, files, or user instructions. Use whenever someone wants to capture what they learned, save a gotcha, or preserve insights for future reference. Also triggers for "remember this", "save this learning", "that was a long session — capture the key findings", or "what do we know about X".
8cmk:worktree-dev-env
This skill should be used when the user asks to "set up local dev", "worktree dev environment", "port conflicts between worktrees", "headless dev mode", "mprocs config", "process-compose setup", or needs to create or iterate worktree-isolated local development environments with deterministic port isolation, coherence validation, interactive and headless service runners, and env file management.
3