What problem does it solve?
This Skill identifies and summarizes inconsistencies between repository code facts, documentation/status facts, and local CLAUDE rule chains to prevent documentation drift and stale guidance. It helps teams keep documentation and local agent guidance aligned with the actual codebase so decisions and status reports remain accurate.
Core Features & Use Cases
- Lane-based discovery: Collects three fact lanes (code, docs, rule chain) from configured paths and normalizes them into comparable inventories.
- Drift detection & classification: Performs pairwise comparisons (code vs docs, code vs rules, docs vs rules) and classifies missing coverage, stale claims, and broken references.
- Prescriptive reporting: Produces a named drift report with source files and recommended edit surfaces while following a policy that prefers doc/rule updates over blind code mutation.
- Use case: Run before a status sync or release to surface documentation mismatches, stale CLAUDE guidance, and missing schema or route references.
Quick Start
Run a subagent-doc-check across the repository to collect code, docs, and CLAUDE rule lanes and produce a consolidated drift report highlighting missing coverage and stale claims.