What problem does it solve? Documentation drifts out of sync with code as projects evolve: file paths get renamed, CLI commands change, config keys disappear, and docs silently become wrong. This Skill verifies that references inside markdown docs still match the actual codebase and surfaces which docs need updating after a code change. ## Core Features & Use Cases - Drift verification (verify mode): Scans markdown docs and deterministically checks file paths, CLI commands, package.json scripts, environment variables, and config keys against the real codebase, emitting a markdown or JSON report with exit codes suitable for CI. - Diff-aware sync (sync mode): Takes a git diff range, reverse-looks-up which docs reference the changed files, and drafts interactive patch proposals that are applied only after explicit per-doc approval. - URL link checking: Delegates external URL validation to lychee running in the background, writing results to a separate drift report without blocking the core check. - Use Case: After renaming a module and deleting a config key, run verify to list every doc still referencing the old names, then run sync on the commit range to get reviewed patch proposals for each affected doc. ## Quick Start Ask the agent to check whether the documentation in the docs folder still matches the current codebase and report any broken file paths, commands, or config keys.