map-codebase

Generate a codebase map by running the skill to walk your repository, identify languages and frameworks, and write structured analysis files such as stack.md and secrets.md into the .vibe-check/analysis/ directory.

Codebase mapping provides a focused, conceptual overview of a repository's stack, architecture, and conventions. You need it for onboarding, pre-audit reconnaissance, or getting a quick readiness snapshot before a deeper assessment run.

You can analyze a large repository by using standard mode exploration, which can spawn a mapper subagent to handle the increased scale and produce structured analysis files without the overhead of a full production readiness assessment.

Yes, codebase mapping supports a compact mode designed for smaller repositories, allowing you to quickly identify entry points, top-level structure, and high-risk areas without spawning unnecessary subagents.

Mapping a codebase produces structured markdown analysis files in the .vibe-check/analysis/ directory, including stack.md, secrets.md, auth.md, and ai-security.md, which document detected capabilities for downstream assessments.

A conceptual codebase map provides a high-level readiness snapshot and pre-audit reconnaissance but does not replace a full production readiness assessment, meaning it may not detect deep architectural vulnerabilities or complex compliance issues.