update-doc

Documentation drift occurs when code changes but docs remain outdated. This tool searches the codebase for current implementations and updates existing documentation to reflect the latest code, reducing drift across multiple pages.

You can update outdated documentation by running this tool to scan source files and align page content. It presents before and after changes for your review, ensuring frontmatter and terminology match the actual scope before applying.

Yes, you can review changes before they are applied. The tool generates before and after comparisons for your approval, ensuring frontmatter and terminology align with current code implementations before finalizing updates.

Yes, documentation sync respects frontmatter definitions and applies custom terminology. It reads contextual files like .devdoc/context.json to ensure name and description frontmatter remain consistent with the actual scope of your codebase.

The best way to detect outdated terminology and feature flags is using a docs-sync tool that reads context files and scans the codebase. It identifies duplicates and aligns terminology to ensure documentation reflects current implementations.

To reorganize docs navigation during a multi-page sync, the tool updates content to match source files and adjusts the documentation structure as needed. This ensures navigation remains logical while reflecting current code implementations.