What problem does it solve? Software changes often silently invalidate existing documentation, leaving readers with false guidance. This Skill traces a code, CLI, schema, or workflow change to every affected reader-facing contract and decides whether documentation needs no update, an immediate fix, or a fix plus a later synthesis. ## Core Features & Use Cases - Change-to-documentation tracing: Inspects diffs against a specified base and maps altered APIs, CLI options, schemas, and workflows to affected docs pages, navigation, and examples. - Three-outcome decision: Returns exactly one of no impact, update now, or update now + synthesis, with evidence-based reasoning and bounded deferred work. - Authorized bounded edits: When edits are permitted, applies minimal documentation corrections while preserving repository format, terminology, and generated-file policy, then validates with the project's own checks (Sphinx builds, doctests, Ruff, Vale). - Use Case: Before merging a pull request that renames a CLI flag and changes a default value, run this Skill against origin/main to find every tutorial, reference page, and help text that must change, and apply the corrections in the same branch. ## Quick Start Use $documentation-impact-review to review this branch against origin/main and make the documentation updates required for current correctness.
