docs-sync

Documentation coverage auditing compares code and configuration files against the docs/ directory to surface missing mentions of options, environment variables, and behavioral changes. This process identifies gaps and outdated information by mapping src/ features to existing documentation pages.

Code-to-doc mapping requires diffing the current development branch against main. The system analyzes changes, maps new or changed features to relevant documentation pages, and proposes targeted edits with evidence and cross-links for reviewer approval.

Yes, English-language docs under docs/** are supported. The audit compares main branch features and configuration against the documentation structure to identify missing mentions of options, environment variables, and behavior.

The best way is running a docs-sync pass against the current branch. This produces a Docs Sync Report containing evidence, suggested edits, and cross-links designed for reviewer approval before any changes are applied.

Yes, docs-sync audits MkDocs documentation structures by comparing code and configuration against the docs directory. It surfaces missing mentions of options and behavior, proposing targeted updates to align documentation with current source code features.