lrh-doc-work

Keeping documentation in sync with merged pull requests involves analyzing recently merged work to map technical changes into Diataxis documentation quadrants, validating updates through linting, and proposing changes via a pull request.

Diataxis classification maps technical changes from merged work into four documentation quadrants: Tutorials, How-to guides, Reference material, and Explanations. This ensures structural consistency and accuracy when updating repository docs.

You need the GitHub CLI (`gh`) installed to automate repository documentation updates, as the skill depends on it to analyze merged pull requests and propose validated documentation changes via GitHub.

You can validate documentation updates before submitting a pull request through automated linting and testing, with human-in-the-loop confirmation gates ensuring documentation quality and accuracy prior to PR submission.

Preventing documentation drift after landing code changes is best achieved by automatically analyzing merged workstreams, mapping updates to Diataxis documentation quadrants, and validating linted changes before submitting a pull request.

Repository documentation remains stale after merging new features when technical updates are not automatically mapped to Diataxis documentation quadrants. Automating this analysis and validating updates via pull requests resolves the documentation drift.