What problem does it solve?
Documentation for the Crowi site (apps/crowi-site) drifts out of sync with the main branch as features and fixes are merged, leaving user-facing docs missing new behavior or describing outdated behavior. This Skill performs a periodic maintenance pass that both documents recent user-visible changes and hunts down stale descriptions by verifying claims against the actual code.
Core Features & Use Cases
- Delta-driven doc updates: Extracts user-visible changes since the last sync (tracked via a watermark in .feature-state/docs-sync-state.json) using changesets and commit history, then writes new documentation from the actual implementation code rather than commit messages.
- Staleness sweep with claim verification: Cross-checks existing docs claims against env schemas, config files, renderer registrations, package.json scripts, and port definitions, then applies a fix-or-drop policy to every finding.
- Bilingual parity and build gates: Enforces simultaneous ja/en page updates, runs a parity check on changed docs, and validates with the Fumadocs site build, lint, and type-check before committing.
- Use Case: Before a release pre-flight, run the Skill to catch up the crowi.wiki docs on three recently integrated features, fix two outdated config descriptions, and advance the sync watermark in one commit.
Quick Start
Run the crowi-docs-refresh skill to bring the site documentation up to date with the latest merged changes on main and clean up any stale descriptions.