minime-sync
~/.copilot is the live setup; ~/code/minime/copilot/ is its versioned
mirror on master, installed elsewhere with make copilot-install. This
skill copies live → mirror and commits on a sync branch off master
(linus refuses to commit on master); the user pushes it and merges it.
Start every shell description with the calling agent's [name]. Run every
command from ~/code/minime in a subshell ((cd ~/code/minime && …), never
a bare cd, which would move the session's directory): the destinations are
versioned, so the permission hook lets them through. Never push.
1. Preconditions
(cd ~/code/minime && git branch --show-current && git status --short)
Stop and tell the user if the tree is not clean (show git status:
uncommitted work in the mirror is not yours). Then, by branch:
master: start a sync branch from it,(cd ~/code/minime && git switch -c copilot-sync-$(date +%Y%m%d-%H%M)).copilot-sync-*: an earlier sync not merged yet; keep committing on it.- Anything else: stop and ask the user, since it is someone else's work.
2. Copy
Copy only what the mirror tracks (never permissions-config.json,
config.json, session-state/ or logs: they are machine state).
(cd ~/code/minime \
&& cp ~/.copilot/agents/*.agent.md copilot/agents/ \
&& for s in ~/.copilot/skills/*/; do n=$(basename "$s"); d=copilot/skills; \
[ -d common/skills/$n ] && d=common/skills; cp -r "$s" $d/; done \
&& cp -r ~/.copilot/hooks/. copilot/hooks/ \
&& cp ~/.copilot/settings.json ~/.copilot/copilot-instructions.md copilot/ \
&& cp ~/.bash_copilot copilot/bash_copilot \
&& cp ~/.local/bin/kent ~/.local/bin/argyris copilot/bin/ \
&& cp ~/.local/bin/linus ~/.local/bin/spec-check ~/.local/bin/signal-check common/bin/ \
&& cp ~/.local/share/minime/signals/*.schema.json common/signals/)
Then look for files the live setup no longer has (renamed or deleted):
(cd ~/code/minime && for d in agents hooks; do diff -rq ~/.copilot/$d copilot/$d; done \
&& for s in copilot/skills/*/ common/skills/*/; do diff -rq ~/.copilot/skills/$(basename $s) $s; done \
&& diff -rq ~/.local/share/minime/signals common/signals)
Skills shared with the Claude Code workflow live in common/skills/; the
loop above copies each live skill to the folder that already holds it, and a
new skill to copilot/skills/. A change to a skill in common/ reaches the
Claude Code workflow too: say so to the user before committing it.
An Only in copilot/… line is a file removed or renamed live: if renamed,
git mv old new before copying (history follows the file), otherwise
git rm it; ask the user when you cannot tell. No Only in ~/.copilot/…
line may remain after the copy.
3. Check
(cd ~/code/minime && git add -N . && git status --short && git diff --stat)
- Nothing changed: say the mirror is already in sync and stop.
- A new agent or skill, or a renamed one: update the tables in
README.md; a new top-level file incopilot/: add its install line to thecopilot-installtarget of theMakefileand mention it in the README. - Show the user the
git diff --stat(and the diff ofREADME.md/Makefileif you edited them).
4. Commit with the linus command
Every change is a new commit: never a fixup, never an amend. Write a
Conventional Commits message with the copilot scope: a one-sentence subject
(feat(copilot): …, fix(copilot): …, docs(copilot): …), a blank line and
one or two C2-level English sentences saying what changed and why. The
subject is at most 72 characters: the prefix feat(copilot): already takes
15, so write a description of at most 50 characters, naming only the main
change (the agents involved and the details go in the body). Validate it
first, and on a failure shorten it by the characters reported:
(cd ~/code/minime && linus check-message <<'MSG'
<subject>
<body>
MSG
)
Then commit with one readable command, since the user reads the message in
the permission prompt: the changed paths one per line, the message as a
quoted heredoc (linus appends the Copilot trailer), and --model <id>
only if your model differs from the one in ~/.copilot/settings.json.
(cd ~/code/minime && linus commit --phase other \
copilot/agents/foo.agent.md \
README.md \
<<'MSG'
<subject>
<body>
MSG
)
Report the new commit hash and the sync branch, confirm the tree is clean,
and remind the user to push the branch and merge it into master.