What problem does it solve? Documentation drifts out of sync with code after refactors, leaving stale endpoint paths, renamed environment variables, and outdated table columns in specs. This Skill pressure-tests markdown docs against the actual codebase so discrepancies are caught with file-and-line evidence instead of being discovered by users. ## Core Features & Use Cases - Doc-vs-Code Auditing: Cross-references statements in docs/ markdown files against live entities, DTOs, controllers, and services using Read, Grep, and Glob. - Structured Verdicts: Classifies each finding as ACCURATE, STALE, CONTRADICTED, or MISSING_SPECS with quoted doc statements and code evidence links. - Use Case: After refactoring a NestJS API, run an audit on docs/04-开发指南/ to verify that endpoint paths, DTO fields, and environment variables cited in the guides still match the controllers, then receive a revision-ready report. ## Quick Start Audit the specification file docs/api-spec.md against the current NestJS server code and report any stale or contradicted statements with code evidence.