Xcode Sync
Xcode fleet sync: signed archives, compatibility, install, selection, first launch.
Install
npx skills add steipete/agent-scripts --skill xcode-sync -g -a claude-code -y- Repository
- steipete/agent-scripts7.4k
- Category
- Mobile
- Updated
- 5d ago
- License
- MIT
- Context cost
- Mediumabout 2,054 tokens
- Runs scripts
- Yes, review before use
What it does
Xcode fleet sync: signed archives, compatibility, install, selection, first launch.
Xcode Sync
Synchronize exact Xcode builds across Peter's supported Macs. Use $remote-mac for fleet topology and SSH rules.
Inventory
- Read
~/Projects/manager/computers.yaml; use livetailscale status --jsonfor reachability/IPs. - Exclude handed-off and unknown hosts. Verify
hostname, user, macOS, architecture, and hardware UUID before writes. - Deduplicate Tailscale nodes by hardware UUID; one Mac may have multiple live node records.
- Run
scripts/xcode-host-inventory.shlocally or remotely:
skills/xcode-sync/scripts/xcode-host-inventory.sh
ssh -o RequestTTY=no -o RemoteCommand=none HOST 'bash -s' \
< skills/xcode-sync/scripts/xcode-host-inventory.sh
Treat unreachable hosts as pending, not synchronized. Try live Tailscale IP, Tailscale SSH, then mDNS/LAN only when network topology permits.
Simulator hygiene
Every fleet Mac must pass the simulator-hygiene audit, including worker Macs where the correct result is not-applicable because Xcode and simctl are absent. Apple CoreSimulator's own classifications are authoritative: remove runtime images reported by simctl runtime delete --outdated --dry-run or --unusable --dry-run, plus simulator devices attached to unavailable runtimes. Do not classify a runtime as stale from its version number alone; stable and beta Xcodes can legitimately need different runtime generations on the same Mac.
Run the dependency-light audit locally or stream it to a remote Mac:
skills/xcode-sync/scripts/xcode-simulator-hygiene.sh
ssh -o RequestTTY=no -o RemoteCommand=none HOST 'bash -s' \
< skills/xcode-sync/scripts/xcode-simulator-hygiene.sh
