docs-sync

To check if documentation is outdated, you can audit your documentation coverage against the main branch implementation. This process compares public exports, configuration options, and environment variables against existing docs to identify missing or incorrect information.

The best way to sync mkdocs.yml with code changes is to analyze public exports, configuration options, and CLI commands against the existing documentation structure. This identifies discrepancies and proposes targeted structural updates to improve alignment.

To find missing documentation for new features, compare the main branch code against the 'docs/' directory. This audit flags undocumented exports and configuration options, proposing targeted additions to ensure complete documentation coverage.

Yes, documentation synchronization works with environment variables and CLI commands by analyzing them against existing documentation pages. It detects discrepancies and proposes updates to ensure these technical configurations are accurately reflected.

You can automatically generate proposed structural updates for your docs directory by auditing it against your codebase. The analysis identifies coverage gaps and suggests specific changes to align the documentation with the main branch implementation. Yes, you can automatically generate proposed structural updates for your docs directory by auditing it against your codebase. The analysis identifies coverage gaps and suggests specific changes to align the documentation with the main branch implementation.

You should run a documentation audit on your codebase after adding a new feature or modifying configuration options. This ensures your documentation accurately reflects the current state of the code and prevents outdated information.