doc-updater

To keep documentation in sync with code changes in the same commit, you can use a 5-step doc-sync workflow that enumerates file diffs, routes changes to owning docs, applies updates with dated markers, and verifies the results in-commit.

Documentation drift happens when code changes leave co-located docs outdated. Prevent drift by binding code edits to their canonical owning documentation and enforcing ownership-based updates within the same commit.

To fix stale references after renaming or deleting code, run a stale-reference sweep that detects outdated mentions and verifies all documentation updates landed correctly before reporting completion.

Yes, you can update documentation for multiple programming languages in a single repository. The workflow handles edits across languages and tooling by routing diffs to the canonical owning docs for each changed file.

The best way to automate documentation ownership routing is to use a routing table that maps changed files to their canonical owning docs, ensuring updates are applied and verified with a dated change marker in the same commit.