acquire-codebase-knowledge

To generate codebase documentation for onboarding, you can use static analysis to map architecture and conventions, automatically producing structured reports like STRUCTURE.md, ARCHITECTURE.md, and CONVENTIONS.md to guide new developers.

Static code analysis for mapping architecture scans the source without executing it, identifying structural dependencies and conventions to output detailed documentation covering the project's integrations, testing setup, and overall design.

Yes, you need Python 3.8+ and git installed to execute the codebase mapping scripts. The scripts must be run from the project root directory to accurately analyze the repository structure.

Yes, you can focus specifically on architecture by running the skill with the argument `-a "architecture only"`, bypassing the generation of other reports like STACK.md or TESTING.md.

The best way to identify conventions and integrations is by running static code analysis that generates dedicated CONVENTIONS.md and INTEGRATIONS.md reports, providing clear guidelines for new team members.

Static code analysis limitations include missing runtime behaviors and dynamic execution paths. The generated CONCERNS.md report highlights known issues and structural concerns, but manual review is still required for complex logic.