codemap

Repository mapping scans a project to select relevant source and config files, creating a hierarchical codemap for each folder. This provides folder-level understanding for unfamiliar codebases and bootstraps documentation scaffolding to identify directories needing deeper analysis.

Hash-based change detection for repository mapping stores file state in a local JSON file. On subsequent runs, it compares current file hashes against this saved state to precisely identify which files were added, removed, or modified since the initial mapping.

Yes, you can migrate legacy cartography state into a new codemap format. The repository mapping process automatically upgrades older JSON state files into the current format without losing continuity during your workflow.

The best way to bootstrap documentation scaffolding is to run a repository mapping process that generates hierarchical codemaps. This creates an empty scaffold for affected directories, giving you a structured starting point for project documentation.

Yes, repository mapping works with incremental mapping workflows by applying deterministic file selection and hash-based change detection. It refreshes the codemap and updates affected directories without requiring a full rescan of the entire codebase.

You need empty codemap scaffolding for affected directories when initializing documentation in newly added folders or when incremental mapping detects changes. It provides a structured placeholder to guide subsequent manual documentation efforts.