What problem does it solve? Writers maintaining MariaDB documentation need to know whether a code change (an MDEV ticket, DOCS ticket, or server PR/commit) is user-facing and which doc pages it affects before drafting anything. This Skill performs that triage step: it reads the actual diff, classifies the user-facing surface, and reports whether docs are needed, which pages to edit, and which claims must be verified. ## Core Features & Use Cases - Source-of-truth analysis: Resolves MDEV/DOCS tickets or GitHub PRs to the exact commit that introduced the change and analyzes the diff, not just ticket prose. - Impact classification: Detects new system variables, SQL syntax, startup options, error messages, behavior changes, and deprecations, then decides YES/NO/MAYBE on documentation need. - Fact-check report skeleton: Writes a triaged report with PENDING claim rows (source file:line @ commit SHA) to an external reports directory for the drafting step to consume. - Use Case: Given "what docs does MDEV-37456 need?", the Skill fetches the ticket, pins the introducing commit in the local MariaDB/server repo, greps the docs for affected symbols, and outputs an impact report naming the exact pages to edit. ## Quick Start Ask the assistant to analyze the documentation impact of MDEV-XXXXX or a given MariaDB server pull request.
