What problem does it solve? Keeping published chapter content in sync with an upstream editing repository is error-prone: files get copied manually, outdated dated versions linger, and edits made directly on the platform side can be silently overwritten. This Skill automates a safe, incremental, one-directional sync of chapter section files and lab questions into the publishing platform. ## Core Features & Use Cases - Incremental file sync: Copies only newer or missing files, deletes superseded dated versions, and regenerates index.md so each chapter folder stays flat and current. - Conflict detection: Uses a per-chapter .sync-manifest.json with SHA-256 hashes to detect destination-side edits before overwriting, offering overwrite, keep, or diff choices. - Safety guardrails: Never syncs lab answer files, flags exposure risks, supports --dry-run previews, --force repair, and --all batch mode, and only offers the heavy bookData regeneration with explicit approval. - Use Case: After finishing edits to chapter 4 in the BITM330 editing repository, run the sync to copy the updated main section and lab questions into the platform, regenerate index.md, and get prompted to rebuild bookData.ts. ## Quick Start Sync chapter 3 from the editing repository into the platform by asking to run chapter-sync with chapter number 03, optionally adding --dry-run to preview changes first.