review-docs

Documentation drift is detected by validating reference docs against repository state and pattern registries. This identifies stale ground-truth claims and residue from past migrations, generating a consolidated staleness report for maintainers to triage.

Documentation drift occurs when reference docs become misaligned with repository state. Audit for staleness to catch outdated CLI references, deprecated patterns, and invalid ground-truth claims across your documentation suite before they mislead users.

Documentation is validated against data/docs-patterns.yml, nextflow.config, and linked references using a validation tool. This cross-referencing checks CLI references and lint IDs to ensure documentation accurately reflects the current repository configuration.

Yes, validation checks apply across the entire repository to catch cross-skill documentation drift. This ensures consistency across all skills by verifying that linked references and ground-truth claims match the actual repository state.

Run a validation process that checks reference documentation against repository state to generate a consolidated staleness report. This provides actionable triage notes, enabling targeted updates to keep documentation aligned with the codebase.