update-docs

You can automatically sync documentation by reading package.json scripts and .env.example as source-of-truth files to generate up-to-date docs/CONTRIB.md and docs/RUNBOOK.md, ensuring a single source of truth across development and deployment contexts.

The best way to identify obsolete documentation is to audit docs that have not been touched in 90 or more days, flagging them for manual review against the authoritative package.json and .env.example references.

Generating docs from .env.example and package.json works by extracting environment variables and script definitions from those authoritative files, then building unified documentation sets that reflect the current codebase configuration.

Yes, this docs-sync approach applies to monorepos containing package.json scripts and an .env.example, reading those source-of-truth files across development and deployment contexts to maintain synchronized project documentation.

Project documentation gets out of sync when environment variables and scripts change in package.json or .env.example without corresponding manual updates to docs, which automation solves by using those files as a single source of truth.

No external dependencies are required to automate documentation generation from package.json and .env.example, as the process reads those existing source-of-truth files directly to build the unified docs set.