What problem does it solve? Code documentation drifts out of sync with source files because developers forget to update it. This Skill keeps per-file Markdown docs current by detecting staleness deterministically via CRC checksums and regenerating outdated docs automatically. ## Core Features & Use Cases - CRC-based staleness detection: Each generated doc stores a checksum of its source file in frontmatter; a doc is stale when the current source CRC differs. - JS-orchestrated local pipeline: Queueing, batching, LLM calls, and CRC stamping run in a local JS orchestrator via npx @7n/rules lint doc-files, using a local model with no cloud escalation. - Degraded-mode handling: Docs scoring below the quality threshold are still written with a degraded marker and fresh CRC, so the pipeline never blocks. - Use Case: After modifying several TypeScript files in a repository, run the linter in fix mode to regenerate only the stale docs into docs/ folders next to the code, then review the summary of OK, degraded, and failed files. ## Quick Start Run the doc-files linter from the repository root to regenerate all stale or missing file documentation.