acquire-codebase-knowledge

Onboard new engineers by generating a structured knowledge bundle from verifiable repository data. This creates a canonical seven-document set covering stack, structure, conventions, and testing to accelerate contributor alignment.

Map codebase integrations and conventions safely by anchoring every claim to specific files or terminal outputs. The generated documentation strictly avoids unsupported inferences and clearly marks any unknown elements.

Repository-wide discovery mapping works by scanning verifiable files and terminal outputs to populate seven documentation templates. It derives architecture, structure, and testing facts directly from the repo, ensuring full traceability.

Codebase architecture discovery generates seven markdown templates: STACK.md, STRUCTURE.md, ARCHITECTURE.md, CONVENTIONS.md, INTEGRATIONS.md, TESTING.md, and CONCERNS.md, all populated with evidence from repository files.

You do not need external dependencies to map and document your codebase. The discovery process relies solely on verifiable repository files and terminal outputs to generate the structured documentation set.

Avoid automated codebase documentation generation if your repository lacks sufficient source files or terminal outputs to verify claims, as the process strictly requires traceable evidence and flags unknowns.