wiki-synclisted

Multi-machine git sync for the wiki: pull, merge with custom drivers (log.md union+sort), push. Local sync lock + force-push detect + identity check + per-machine sync reports under ~/.kata/sync-reports/. Hard stops on import-in-progress, merge-in-progress, identity mismatch, force-push detected, unrelated histories. NEVER touches anything in the wiki repo without committing it first; reports go to ~/.kata/ to avoid self-conflict.
litianyi-007/kata · ★ 0 · Code & Development · score 73

Install: claude install-skill litianyi-007/kata

# wiki-sync Pull-merge-push your wiki across machines. Designed for the v1.7.2 multi-project layout (`~/.llm-wiki/{project}`), one git remote per project. Each machine's lock and sync reports are namespaced by wiki slug, so you can run wiki-sync on multiple project wikis concurrently. > The cron friend of `wiki-dream`. Recommended chain: `wiki-sync --auto > && wiki-dream`. If sync fails or stops on a conflict, dream doesn't run > — that's by design (PRD-v1.8 §11.6). ## When to use - Multi-machine workflow: laptop ingests on Wed, desktop on Sat, you want a single coherent wiki on Sunday morning - Returning from a trip: one `wiki-sync` brings everything that the other machine pushed since you left - Cron-driven weekly: `0 23 * * 0 wiki-sync --auto && wiki-dream` - Pre-flight before starting work: `wiki-sync --dry-run` shows what *would* happen ## When NOT to use - Single-machine wiki without a remote — `sync.enabled: false` in SCHEMA.md or just don't add a `sync:` block; wiki-sync becomes a no-op - During an active `wiki-import` — preflight refuses to operate while `.wiki-import-lock` is fresh or `.wiki-import-checkpoint.json` is present (signals: "import was interrupted, resume or clean before sync") - During an active `git merge` / `git rebase` / `git cherry-pick` — preflight refuses; finish the in-flight git operation first ## Implementation `plugin/scripts/wiki_sync.py` owns the entire orchestration: lock / stash with SHA tracking / fetch / ancestry c