What problem does it solve? Documentation drifts out of sync with code as projects evolve: symbols get renamed, features get removed, links break, and CLI flags change, but nobody notices until a reader hits a dead end. This Skill runs a mechanical, read-only lint over the narrative docs tree and reports every drift finding with path:line locations, without rewriting any prose. ## Core Features & Use Cases - Seven mechanical checks: broken code references, removed-feature docs, orphan files, documentation TODOs, markdown link integrity (including anchors), stale CLI invocations verified against the tool's real help output, and structural issues like table-of-contents drift and heading-hierarchy skips. - Scoped or full runs: lint the entire docs root plus hand-authored root files like README.md, or scope the run to docs intersecting a specific change-set before a merge. - Report-only output: emits a structured markdown report with findings grouped by check type; it never modifies, deletes, or auto-fixes any file. - Use Case: After a refactor that renamed several functions and removed a CLI flag, run the lint before proposing the change for merge to catch every doc that still references the old names. ## Quick Start Run a doc lint over the docs directory and README to report broken code references, dead links, and stale CLI invocations before I merge this change.
