codebase-map

name	codebase-map
description	Map an unfamiliar codebase into stack, architecture, structure, conventions, testing, integrations, and concerns before changing it.

Codebase Map

When To Use

• Starting work in an unfamiliar repository.
• User asks what the codebase does or where to make a change.
• A feature spans multiple modules and hidden conventions matter.

Workflow

1. Start with manifests, README, architecture docs, and entrypoints.
2. Outline major directories and ownership boundaries.
3. Identify stack, runtime commands, testing approach, and build artifacts.
4. Find representative files for patterns instead of reading everything.
5. Note integrations, generated code, config, and stateful resources.
6. Produce a compact map with uncertainties.

Preferred Tools

• as_project_analyze
• as_file_tree
• as_code_outline
• as_file_search_text
• as_file_read

Output

• stack
• architecture
• structure
• conventions
• testing
• integrations
• concerns