docs-generator

It audits existing documentation to assess coverage and accuracy, analyzes the codebase to detect architecture and dependencies, then generates CLAUDE.md and a structured docs/ directory covering architecture, standards, and onboarding.

To create a CLAUDE.md and organize docs, the generator analyzes your code to produce a living table of contents in CLAUDE.md and bootstraps a structured docs/ directory with architecture, standards, and onboarding content.

Yes, this automated documentation generator applies to diverse codebases from small repos to large monorepos, detecting architecture, patterns, and data flow to produce structured documentation at scale.

Evidence-based documentation works by auditing source code, detecting architectural patterns, and producing a structured CLAUDE.md plus a scalable docs/ hierarchy based on actual code analysis rather than manual input.

No dependencies or components are required to set up automated codebase documentation; you run the generator directly on a repository to produce the CLAUDE.md file and the docs/ folder structure.

The best way to fill documentation gaps is to audit existing documentation for coverage and accuracy, then analyze the codebase to detect architecture and patterns, generating structured docs to cover missing areas.