codebase-mapping

To map codebase architecture, the skill reads package manifests, README, and entry points, outputting structured files like ARCHITECTURE.md and INDEX.md into a .codebase/ directory to explain how the project works.

Document an unfamiliar repository by running a stepwise mapping process that inspects manifests, maps entry points, and outputs documentation covering conventions, dependencies, and top-level directories.

Generating architecture documentation speeds onboarding by providing new contributors with clear entry points, key configuration files, and project conventions, reducing the time needed to understand cross-module workflows.

Yes, you can map conventions and dependencies for cross-module work. It generates DEPENDENCIES.md and CONVENTIONS.md to support feature planning and auditing across different parts of the codebase.

You need accessible package manifests, a README, and identifiable entry points within the repository. The mapping process reads these to generate the structured .codebase/ documentation output.