verify-claims

Re-verify fact-check report claims against MariaDB source code at recorded SHAs.

28|115|Updated Jan 28, 2025
One-click install
npx skills add https://github.com/mariadb-corporation/mariadb-docs --skill verify-claims-mariadb-corporation
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: verify-claims
Source: https://github.com/mariadb-corporation/mariadb-docs/tree/main/.claude/skills/verify-claims
Command: npx skills add https://github.com/mariadb-corporation/mariadb-docs --skill verify-claims-mariadb-corporation

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Documentation fact-check reports can go stale or be wrong, and reviewers in a later session have no way to confirm each documented claim is still backed by source code. This Skill independently re-proves every claim in a report against the MariaDB source at the recorded SHA and the current ref, surfacing drift before a doc PR is approved or merged. ## Core Features & Use Cases - Per-claim re-verification: Confirms each claim's cited source evidence still holds at the recorded SHA using read-only git commands, without trusting the original verdict. - Drift detection: Compares the recorded SHA against the current ref head and the live doc page, assigning statuses like STILL-VERIFIED, DRIFTED, SOURCE-MOVED, DOC-CHANGED, or UNVERIFIABLE. - Audit snapshot: Writes a dated verification run file next to the report while never editing docs, source, or the report itself. - Use Case: Before merging a doc PR another writer drafted for DOCS-1234, run the audit to confirm every claim is still source-proven and get an ALL CLEAR or NEEDS ATTENTION verdict. ## Quick Start Verify the claims for DOCS-1234 and tell me whether the fact-check report is still source-proven.

Frequently Asked Questions about verify-claims

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a documentation fact-check report against source code?▼

Provide a DOCS or MDEV key and the Skill locates the report in the configured reports directory, then re-checks each claim against the cited source file and line at the recorded SHA using read-only git commands. It outputs a per-claim status table and a final verdict.

How to detect documentation drift after source code changes?▼

The Skill re-resolves each fact at the current ref head and compares it with the recorded SHA, marking rows DRIFTED when the current source differs. It also checks the doc page itself and flags DOC-CHANGED when the page no longer contains the claim.

Does claim verification work without a configured MariaDB source repo?▼

No. Source repos must be configured in .claude/doc-sources.local.json with paths and refs. Rows for products without a configured source, or claims lacking a SHA, are reported as UNVERIFIABLE rather than assumed true.

Can the verification audit edit the docs or the report?▼

No, the audit is strictly read-only for docs, source, and report.md. The only file it writes is a dated snapshot under the report's runs directory, and fixes for drift are handed back to the doc-ticket workflow.

What happens when a cited source line no longer exists at the recorded SHA?▼

The claim is marked SOURCE-MOVED, meaning the evidence pointer is wrong. The Skill attempts to re-grep the symbol at that SHA before assigning the status, and the row counts toward a NEEDS ATTENTION verdict.