update-docs

Documentation synchronization automates updates by reading package.json and .env.example as source-of-truth files to generate accurate setup instructions and environment variable references. Running the sync command updates local repository documentation automatically.

Generating a RUNBOOK.md is automated by reading your project's source-of-truth files and producing deployment and monitoring documentation. This ensures operational runbooks stay synchronized with your package.json configuration without manual writing.

Yes, environment variable documentation is generated automatically by parsing .env.example files. The synchronization process reads these source-of-truth files and creates accurate references for all defined variables in your local repository.

Development guidelines in CONTRIB.md are kept updated through automated documentation synchronization. The tool reads your package.json and generates contribution documentation that reflects current scripts and setup instructions without manual maintenance.

Yes, documentation synchronization works without additional dependencies or plugins. The tool operates independently using built-in scripts to read source-of-truth files and generate documentation, requiring no external packages to function.

Documentation synchronization should be run whenever package.json or .env.example files change. This ensures generated documentation like RUNBOOK.md and CONTRIB.md stays accurate and reflects the current source-of-truth configuration.