What problem does it solve? Documentation drift is inevitable in a fast-moving C++ game engine: README counts go stale, wiki pages describe deleted classes, and generated API docs diverge from code. This Skill provides the complete pipeline for keeping SparkEngine's five documentation layers (handwritten prose, generated AUTO regions, validators, CI enforcement, and publication) consistent with the actual source tree. ## Core Features & Use Cases - Layer-aware drift repair: Identifies whether a wrong statement lives in handwritten prose, generated AUTO regions, or the readiness contract, then applies the correct fix (edit prose vs. re-run a generator) instead of editing generated output that will be overwritten. - Regeneration and validation commands: Verified invocations for docs/update-all-docs.sh, docs/sync-wiki.sh, API doc generation, symbol indexes, README badge counts, and validators like check-wiki-nav.sh, validate-prompts.sh, and tools/site-data/validate.py. - Readiness handoff governance: Explains the site-data contract vocabularies (implementation, verification, support, release states) and why ENGINE_READINESS_HANDOFF.md must be regenerated, never hand-edited. - Use Case: A CI run fails with "sync-wiki check exited 1". Use this Skill to identify the stale AUTO region, run docs/sync-wiki.sh sync, verify with the check mode, and confirm the publish-wiki validate job will pass. ## Quick Start Ask the assistant to check whether the SparkEngine wiki and README counts are stale and regenerate any out-of-date generated documentation sections.
