kenjaku: Skill for Claude Code

/sync — Cross-machine repo synchronization

User command. Useful when working on several machines (personal / work laptop) and you want to pull in changes pushed from the other without leaving the session.

When to use it

• When you've worked on another machine and want to pull the changes in here.
• Mid-session, without having to quit and relaunch Claude Code.
• Complements the SessionStart hook (which pulls at startup) for mid-session cases.

ℹ️ Requires a configured git remote (origin). For purely local use, this skill is useless.

Procedure

Step 1 — Local state

git status --porcelain

Clean → go to step 3. Dirty → step 2.

Step 2 — Commit local changes

git add .
git commit -m "auto: vault/claude sync"

Creates a safe restore point before the rebase.

Step 3 — Fetch and rebase

node scripts/set-active-universe.mjs current   # remember it: step 5 compares
git rev-parse HEAD                             # remember this sha: step 5 passes it as --before
git fetch origin
git rebase origin/$(git branch --show-current)

Success → summary + step 5. Conflict → step 4.

Read the active universe before rebasing. The pull can carry a context switch made on the owner's other machine (it is committed state — ADR 0034), and step 5 can only say so by comparing. At session start the same thing is handled deterministically by a hook; mid-session, this skill is the only channel.

Step 4 — Conflict handling

1. List the conflicting files: git diff --name-only --diff-filter=U
2. Show the diff of each with context.
3. Ask the user:

   Conflict on N file(s). Options:

   • merge: I resolve and we continue the rebase
   • abort: git rebase --abort — back to the previous state (the local commit is safe)

4. If merge: resolve intelligently (vault content = often append-only → keep both versions), git add the resolved files, git rebase --continue.
5. If abort: git rebase --abort, report that the local commit is intact, stop.