メニュー
Codebase analysis and mapping for autonomous agent understanding. Builds structured maps of project stack, architecture, conventions, testing, integrations, and concerns.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
| name | ct-codebase-mapper |
| version | 1.0.0 |
| description | Codebase analysis and mapping for autonomous agent understanding. Builds structured maps of project stack, architecture, conventions, testing, integrations, and concerns. |
| category | recommended |
| tier | 1 |
| protocol | null |
| dependencies | [] |
| compatibility | ["claude-code","cursor","windsurf","gemini-cli"] |
| triggers | ["codebase map","analyze codebase","understand project","brownfield analysis","project structure"] |
Structured codebase analysis for autonomous agent understanding.
| Goal | Command | Cost |
|---|---|---|
| Quick analysis | query admin map | ~500 tokens |
| Deep analysis + store | mutate admin map | ~800 tokens |
| Focus on one area | query admin map {focus: "concerns"} | ~300 tokens |
| CLI | cleo map / cleo map --store | — |
cleo map
Returns structured CodebaseMapResult with stack, architecture, structure, conventions, testing, integrations, and concerns.
cleo map --store
Same analysis, but stores patterns, learnings, and observations to brain.db. Tagged with source: 'codebase-map' for filtering.
cleo map --focus concerns
Focus areas: stack, architecture, structure, conventions, testing, integrations, concerns.
cleo map --store to build brain.db contextcleo init --map-codebase runs analysis during initializationquery admin map {focus: "concerns"} for TODOs and large files{
projectContext: ProjectContext, // From detectProjectType()
stack: StackAnalysis, // Languages, frameworks, deps
architecture: ArchAnalysis, // Layers, entry points, patterns
structure: StructureAnalysis, // Directory tree with annotations
conventions: ConventionAnalysis,// Naming, linting, formatting
testing: TestingAnalysis, // Framework, patterns, coverage
integrations: IntegrationAnalysis, // APIs, DBs, CI/CD
concerns: ConcernAnalysis, // TODOs, large files, complexity
analyzedAt: string
}
Pipeline-aware orchestration skill for managing complex workflows through subagent delegation. Use when the user asks to "orchestrate", "orchestrator mode", "run as orchestrator", "delegate to subagents", "coordinate agents", "spawn subagents", "multi-agent workflow", "context-protected workflow", "agent farm", "HITL orchestration", "pipeline management", or needs to manage complex workflows by delegating work to subagents while protecting the main context window. Enforces ORC-001 through ORC-009 constraints. Provider-neutral — works with any AI agent runtime.
CLEO provider adapter for Anthropic Claude Code CLI. Default export is the adapter class for dynamic loading by AdapterManager. T5240 Use when: (1) calling its 2515 API functions, (2) configuring @cleocode/monorepo, (3) understanding its 1754 type definitions, (4) working with its 104 classes, (5) user mentions "@cleocode/monorepo" or asks about its API.
CLEO task management protocol - session, task, and workflow guidance. Use when managing tasks, sessions, or multi-agent workflows with the CLEO CLI protocol.
Documentation coordinator with CLEO style guide compliance. Routes every canonical-doc write (spec, adr, research, handoff, note, llm-readme) through the docs SSoT via `cleo docs add` / `cleo docs publish` / `cleo docs fetch` — never raw filesystem writes. Coordinates ct-docs-lookup, ct-docs-write, ct-docs-review, ct-spec-writer, and ct-adr-recorder. Use when creating or updating documentation files, consolidating scattered documentation, or validating documentation against style standards. Triggers on documentation tasks, doc update requests, or style guide compliance checks.
Epic planning and task decomposition for breaking down large initiatives into atomic, executable tasks. Provides dependency analysis, wave-based parallel execution planning, hierarchy management, and research linking. Use when creating epics, decomposing initiatives into task trees, planning parallel workflows, or analyzing task dependencies. Triggers on epic creation, task decomposition requests, or planning phase work.
Independent IVTR peer-reviewer role. The Validator is spawned by a Lead AFTER a Worker reports an implementation candidate to verify that every Acceptance Criterion is satisfied by programmatic evidence. The Validator MUST be a different agent instance from the Worker who built the change — same-agent self-attestation is rejected as rubber-stamping. Use when spawned with `subagent_type: cleo-validator` (or equivalent role token) and a target task ID; the Validator pulls the AC list via `validator.ac-pull`, runs the IVTR rubric, then ships exactly ONE binary verdict — `validator.attest` (pass) or `validator.reject` (fail). Triggers: 'validate this implementation', 'run the IVTR rubric', 'attest the acceptance criteria', 'is this PR ready to merge?', any spawn carrying role=validator. Implements ADR-083 §4 (Validator role) and the SG-IVTR-AC-BINDING saga (T10377).