km:doc-review

Reviewing uncommitted documentation changes involves reading staged git diffs to classify edits, checking cross-document alignment across READMEs and guides, and verifying factual claims against implementation sources to prevent misleading commits.

Checking cross-document consistency during a pre-commit review compares staged documentation changes against files like CLAUDE.md, AGENTS.md, and configuration scripts to detect redundant, conflicting, or fragmented information across the repository.

Validating internal links and anchors in markdown documentation requires reading the changed files and their related documents, then systematically verifying that link targets and anchor references resolve correctly within the repository structure.

Fact-checking command examples involves primary-source verification, comparing the documented commands and claims against the actual repository implementation, configuration files, or authoritative external references to ensure factual accuracy.

The documentation review workflow handles partial edits by performing full-document reading alongside systematic change classification, ensuring that localized updates do not break the overall structural clarity of the existing technical guide.

Partial documentation updates introduce inconsistencies when edits to one file omit corresponding changes in related documents, causing conflicting setup instructions or redundant information across READMEs, specs, and configuration guides.