archivist-codebase-inventory

To generate a codebase inventory map, provide the target directory and request an inventory focusing on helper functions, DTO/API mappings, normalization utilities, and runtime boundaries. The map is output to docs/code-audits/inventory/ to support governance reviews and ownership identification.

A codebase inventory is a concise map locating helper functions, DTO/API mappings, and runtime boundaries without altering production code. You need one when planning a focused audit, resolving ownership ambiguities, or reviewing modular interfaces across repository modules and shared utilities.

Yes, this inventory tool supports lightweight generation for both standard codebases and monorepos. It applies targeted search and standardized file patterns to map core constructs across repository modules, services, and shared utilities for governance tasks.

The best way to map DTO and API boundaries is to apply targeted search across the codebase to identify normalization, validation utilities, and runtime boundaries. This generates a standardized inventory file referencing source-of-truth docs for governance.

No, generating a codebase inventory does not modify your production code. It performs a targeted search to create a concise map of helpers, DTO/API mappings, and runtime boundaries, outputting the results to the docs/code-audits/inventory/ directory.