What problem does it solve? User-facing documentation drifts out of sync with the code it describes — READMEs reference deleted paths, links break, code snippets no longer compile, and codemaps go stale after features ship. This Skill keeps README, docs/CODEMAPS/*, architecture docs, and public API docs honest by generating what can be generated from source and flagging what has gone stale instead of silently rewriting it. ## Core Features & Use Cases - Codemap generation and refresh: Builds docs/CODEMAPS/ (INDEX.md plus one file per real area) from actual source files, with entry points, exports, routes, data flow, and freshness timestamps. - Doc-freshness validation: Verifies every path exists, every link resolves, every code snippet matches reality, and staleness is checked against timestamps and last-touching commits. - Salak-sourced dependency sections: Populates codemap dependency sections only from the Salak repo graph with provenance, or omits them honestly — never rebuilds a second dependency graph via madge or AST parsing. - Use Case: After shipping a new API feature, ask the Skill to sync the docs — it regenerates the affected codemaps, flags a stale README snippet, and reports exactly what changed and why. ## Quick Start Ask the assistant to sync the README and regenerate the codemaps for the feature that just shipped, then report which docs were stale.
