What problem does it solve? Documentation drifts out of sync with code as features merge, and naive fixes often rewrite design decisions or historical records that were never wrong. This Skill separates verifiably false claims from design positions, ambiguity, and history before touching anything, so doc fixes are evidence-based and minimal. ## Core Features & Use Cases - Claim inventory and verification: Grep the doc surface for claims (script names, config keys, hook events, counts), then verify each against real files, manifests, scaffolder behavior, and actual scaffolded trees with path:line evidence. - Four-way classification: Classify every finding as verifiably false (fix directly), design position (report only), ambiguous (report only), or historical record (never rewrite), then report A/B/C results to the orchestrator. - Post-merge and compaction audits: Run Phase-5 doc-gap audits after feature merges (worktree setup, fast-forward conflict recovery, grep gates, generated-copy diffs) and README compaction/rewrite passes that extract ground truth from code before rewriting. - Use Case: After a feature merge adds a new CLI backend, audit the README and reference docs against the merged code, fix the one stale wording, and report undocumented auth limitations as decision gaps instead of guessing. ## Quick Start Audit the documentation for drift against the current code and fix only the claims that are verifiably false, reporting the rest.
