cartography

You can automate repository mapping by computing file and folder hashes to detect changes across a codebase. The tool generates a persistent state file and per-folder codemaps, updating documentation as files change to ensure reproducible audits.

Generate per-folder codemaps by initializing repository state to create empty markdown templates. These templates document folder responsibilities, design, flow, and integration points, providing a structured architectural map of your codebase.

Yes, the change detection mechanism respects .gitignore rules and supports user-specified include and exclude patterns. This filtering ensures codemap generation and file hashing focus only on relevant code files.

Yes, this repository mapping approach is designed for codebases of any size. It initializes state, computes hashes, and generates folder-level codemaps regardless of scale, ensuring reproducible audits and consistent change tracking.

Yes, Python 3 is required to run the repository mapping and change detection commands. The tool uses Python scripts and built-in commands like init, changes, and update to maintain an up-to-date map of your repository.

Repository change detection relies on hashing files and storing state in a JSON configuration file. If detection fails, ensure the state file is intact and your include or exclude patterns are correctly configured to track modified files.