docs-revise

To update stale documentation, you can reconcile existing markdown files with your current codebase by revising content based on recent git history and source code, ensuring API documentation accurately reflects actual project functionality.

Finding missing documentation involves comparing the docs directory against the source code to identify undocumented modules, allowing you to create missing markdown files and update the docs README to cover newly discovered components.

You can revise a specific markdown file by targeting its path or component name, which scopes the documentation update to check for broken references and incorrect descriptions in that single file.

Yes, the documentation revision process formats updated markdown files using Prettier, ensuring consistent style and formatting across all created or updated project documentation after reconciling with the codebase.

Yes, you can update all files under the docs directory at once by running the revision scope without specific arguments, which triggers a full code-to-doc discrepancy detection across the entire documentation directory.

You should remove obsolete documentation when the corresponding source code has been deleted, allowing the revision process to identify broken references and delete obsolete markdown files to prevent documentation drift and keep docs accurate.