user-docs-detect-shape

To detect repository structure and metadata, you can analyze file structures and configuration files to determine project type, runtime environment, and license information. This operates across single-package and monorepo environments using read-only file system probing.

Monorepo detection distinguishes root from sub-packages by probing repository file structures and configuration files. This contextual awareness prevents documentation generation errors by ensuring tools operate on the correct project scope and apply accurate metadata.

Yes, you can identify runtime environments like Node, Bun, or Deno and extract package manager details by analyzing repository configuration files. This automated profiling provides accurate technical metadata for documentation workflows.

Read-only file system probing does not modify your repository configuration files. It safely analyzes project metadata, dependencies, and TypeScript versions without altering the underlying file structure or writing new data.

The best way to prepare for documentation generation is to verify project structure and runtime requirements first. Detecting package managers and monorepo architecture ensures the documentation agent applies correct templates and badges.