agent-cc-configs-synclisted
Install: claude install-skill anton-winter-arch/dotagents
# agent-cc-configs-sync
Brings one machine's Claude Code station into line with the spec at
`~/.agents/specs/claude-code/` - the same procedure whether the device is
brand new or just drifted. The spec's `SPEC-CLAUDE-CODE.md` is the source of
truth; its section 0 table maps each seed file to its station path, and a
configured station matches its seeds byte for byte, so every check below is a
`diff`, not a reading exercise. Idempotent by design: on an in-spec station
every phase reports clean and changes nothing.
**Non-destructive throughout.** Nothing on the station is overwritten without
showing the diff and getting the user's pick first. Drift is two-way: the
station may hold a deliberate improvement the spec has not absorbed yet, so
"apply the seed" and "this is a pending spec update" are both valid outcomes.
## Phase 0 - Pull the latest spec, then vet what arrived
Reconciling against a stale spec defeats the point, so update `~/.agents`
first, using the `repo-device-sync` ritual (fetch, deletion pre-flight,
`--ff-only`; divergence or uncommitted work there is stop-and-ask).
Then vet the inbound changes before applying anything: review what the pull
brought in against the station's current state -
```bash
git -C ~/.agents log --oneline <old-head>..HEAD
git -C ~/.agents diff <old-head> HEAD -- specs/claude-code/ | head -200
```
Alert the user up front, before any seeding, to anything breaking, important,
or critical in that delta: changed or removed hooks and permiss