docs-review

Documentation drift is detected by cross-referencing project structures, environment variables, and registry entries against current source code. This skill systematically verifies file paths and cross-document alignment to identify inconsistencies between the codebase and reference material.

Broken links and stale references occur when internal documentation paths and function references become outdated relative to the actual source code. Validating link integrity requires verifying all internal documentation connections against the current repository state.

Validating CLI reference documentation against the repository state requires systematic verification of CLI flags, file paths, and registry entries. This ensures architecture references and command-line documentation remain synchronized with the actual source code.

Yes, task-authoring guides can be audited to identify outdated implementation-tracking language. This status language cleanup ensures documentation reflects current design rather than historical in-flight work across architecture and reference materials.

A comprehensive documentation audit for codebase synchronization requires cross-referencing architecture, CLI reference, and task-authoring guides against the current repository. This detects drift, stale references, and structural inconsistencies across all project documentation.