What problem does it solve? Documentation written from Jira ticket prose alone often repeats feature requests or paraphrases that don't match what actually shipped. This Skill turns a MariaDB DOCS ticket into a concrete documentation edit where every factual claim (defaults, syntax, version notes) is verified against the local MariaDB source code before anything is written. ## Core Features & Use Cases - Ticket-to-Source Traceability: Fetches the DOCS ticket via Jira MCP tools, follows it to the upstream MDEV ticket or GitHub PR, and pins the exact commit SHA used for verification. - Mandatory Claim Verification: Checks system variables, SQL grammar, options, and error codes against files like sql/sys_vars.cc and sql/sql_yacc.yy using read-only git grep/show, marking each claim VERIFIED, CORRECTED, or UNVERIFIED. - Guarded Drafting and Paper Trail: Refuses to draft on main/master, locates the correct .md page, drafts GitBook-formatted edits, and writes a fact-check report to an external reports directory for later posting to the ticket. - Use Case: You receive DOCS-1234 asking to document a new InnoDB variable. The Skill fetches the ticket, confirms the variable's default and scope in the server source at a pinned commit, drafts the reference page edit on the DOCS-1234 branch, and leaves a verification report. ## Quick Start Ask the assistant to document DOCS-1234 by verifying its claims against the local MariaDB server source and drafting the GitBook page edit.
