cartography

You can generate hierarchical codemaps by initializing mapping on a source code repository to compute MD5 file hashes, detect changes, and populate codemap.md templates for each relevant folder. State is persisted for ongoing tracking.

The best way to track file changes is by computing and persisting MD5 file and folder hashes to a state file. This enables reliable change detection to identify modified subfolders and determine which codemaps require updates.

Yes, you can exclude tests, docs, and dependencies when mapping a repository by using include and exclude globs with built-in .gitignore support. This ensures only core source and config files are mapped.

Change detection works by computing MD5 hashes for files and folders, then persisting this state to a JSON file. On subsequent runs, it compares current hashes against the persisted state to detect added, removed, or modified files.

No, you do not need to manually update codemaps. When files change, the mapping process spawns per-folder explorer agents that automatically create or update the codemap.md files for affected folders based on detected modifications.