change-documentation-gate

What problem does it solve?

Prevents releases from shipping with missing, incorrect, or incomplete documentation that would cause user confusion, broken integrations, migration failures, or slower incident recovery.

Core Features & Use Cases

• Documentation impact governance: Determines exactly which artifacts must be updated for a given change type (behavioral deltas, API contracts, migrations, runbooks, ADRs, changelogs, and release communication).
• Release-blocking quality rules: Flags documentation gaps as blocking risks, especially for breaking changes, operational procedures, compliance/audit evidence, and incident documentation sets.
• Audience-appropriate, ownership-backed writing: Requires correct audience targeting and assigns documentation ownership to avoid drift and unmanaged documentation debt.

Quick Start

Ask a maintainer to run the change-documentation-gate to identify which documentation artifacts are blocking for the proposed change and produce a ready-to-ship checklist.