What problem does it solve? Documentation, release notes, and changelogs often drift away from what the code actually does, leading to overstated features, undocumented breaking changes, and examples that fail when followed literally. This Skill systematically detects that drift before it reaches users. ## Core Features & Use Cases - Claim Extraction and Verification: Pulls atomic claims from READMEs, changelogs, release notes, PR descriptions, examples, and docstrings, then locates structural proof in code, tests, routes, exports, and migrations. - Classification of Drift: Labels each claim as SUPPORTED, PARTIALLY_SUPPORTED, UNSUPPORTED, CONTRADICTED, or STEALTH_CHANGE, emitting defects only for material mismatches. - Targeted Checks: Verifies feature, resilience, caching, security, compatibility, and breaking-change claims, including whether renamed routes are imported safely via router objects. - Use Case: Before publishing a release, run this Skill against your changelog and README to confirm every announced feature maps to real handlers and that no undocumented breaking change slipped in. ## Quick Start Review the README and latest changelog entries against the current codebase and report any unsupported or contradicted feature claims.
