hotplex-docs-patrol

Documentation maintenance after code changes is automated by mapping change semantics to affected docs via a registry, applying targeted updates instead of manual checklists. It analyzes new commits by intent to verify content against current code.

Code to docs mapping reads the doc-registry to identify impacted documentation, then verifies content against current code. It tracks a rolling baseline commit to detect feature additions, breaking changes, refactors, and bug fixes for precise remediation.

Run a docs patrol check during release reviews, post-major-PR checks, and for ongoing daily docs status queries. It focuses on documentation reachable from index.md via the BFS boundary produced by the build and discovery tool.

Yes, git diff analysis requires a baseline-driven git change window to identify since-last-run code changes. The skill updates the .docs-patrol-baseline file at the end of each run to maintain a rolling baseline for future change detection.

Validate docs governance and ensure links compile by running make docs-build to verify documentation builds successfully before finalizing. This health check prevents broken cross-references and ensures updated content compiles without errors.

Automated code to docs mapping is limited to processing only docs reachable from index.md via the BFS boundary produced by the build tool. Documentation outside this discovery boundary will not be analyzed or updated during the patrol.