docs-check

Automated documentation checks detect user-facing changes by analyzing git diffs to enforce documentation hygiene, verifying changelog updates or bypass labels before a release.

Changelog governance is enforced by analyzing code diffs to verify changelog updates, generating a JSON checkpoint to provide traceability and ensure documentation hygiene.

No external dependencies are needed to run documentation audits beyond git and standard tooling, which classify changes and generate the required checkpoint file.

A documentation audit generates traceability by analyzing diffs, classifying user-facing changes, and writing a persistent JSON checkpoint file to a designated checkpoints directory.

Yes, you can use bypass labels to skip changelog updates, allowing the diff analysis to classify internal modifications and pass the documentation hygiene checkpoint.

Documentation hygiene checks fail to detect changes when the diff analysis lacks proper context or bypass labels are incorrectly applied during the release validation process.