docs-sync

Documentation audits compare current code and configuration against existing docs to identify missing, incorrect, or outdated coverage. This process maps public behavior and runtime details to the best documentation sections, requiring evidence-backed findings before any edits.

Documentation coverage reviews trace code changes against the docs/ directory to spot coverage gaps and mismatches with implementation. Teams use this branch-aware audit before releases to identify which new features need updates and where those pages should live.

Keeping documentation aligned requires branch-aware doc audits that compare implementation details against existing docs. This approach identifies incorrect or outdated content, recommends precise edits, and proposes structural improvements while maintaining translated-doc boundaries.

Documentation audits follow an approval-first workflow before any edits. The process recommends precise updates, structural improvements, and page placement based on evidence-backed findings, but requires explicit approval before modifying the documentation.

Auditing MkDocs structure involves comparing configuration against existing documentation to identify missing pages and structural improvements. The process traces configuration details to the best documentation sections and proposes placement updates while avoiding translated docs.

Code-to-docs mapping limitations include boundaries on translated documentation, requiring evidence-backed findings for every identified gap. The process focuses exclusively on English docs under docs/ and operates with an approval-first workflow before applying any recommended edits.