hopper-updatelisted

Use when the user asks Hopper to check for updates, upgrade the plugin, reconcile a project after upgrading, migrate .hopper/ config to a newer schema, or explain why an existing project stopped dispatching after a version bump. Triggers: 'hopper update', 'update hopper', 'is hopper up to date', 'migrate my .hopper config', 'my project stopped dispatching after upgrading', 'hopper-dispatch --update-check', '--migrate-config'.
litianyi-007/hopper-plugin · ★ 0 · AI & Automation · score 70

Install: claude install-skill litianyi-007/hopper-plugin

# Hopper Update / Migrate Reconcile three things that drift apart independently: the **installed plugin**, the **project's `.hopper/` config**, and the **vendor CLIs on this machine**. **This never installs plugin code.** Installing is the host's job — Claude Code's marketplace owns the install record and version pin, npm owns the global link, and each of the other hosts has its own path. This skill reports and hands over the host's own upgrade command. ## Steps 1. Locate `hopper-dispatch` from `PATH` or the plugin root near this `SKILL.md`. `--update-check` needs no `.hopper/` project; `--migrate-config` does. 2. `hopper-dispatch --update-check` (add `--offline` to skip the single read-only upstream query; it also degrades on its own when the network is unavailable). Read back all three sections: Install, Upstream, Workspace. 3. **Plugin behind?** Surface the printed upgrade command. Do not run it unless explicitly asked — it replaces the code currently executing. If BREAKING entries were listed, read those `MIGRATION.md` sections and say what changes for this user specifically before they upgrade. 4. **Workspace drifted?** Run `--migrate-config` (dry run is the DEFAULT), show the diff, get confirmation, then `--migrate-config --yes`. 5. **Machine drifted?** `--setup`'s "Vendor binaries" section, and `--binaries --deep` for absolute paths. Several installs of one vendor at different versions is the highest-priority finding: hopper spawns wh