← ClaudeAtlas

local-dev-refreshlisted

Refresh THIS MACHINE's second-shift plugin state - update the second-shift marketplace catalog, then every plugin installed from it ('plugin update' is the verb that actually upgrades - 'install' no-ops as "already installed"), fix project-scope stragglers in the current repo, print the before/after version delta, remind to restart. Scoped to the second-shift marketplace only - other marketplaces on the machine are left untouched. Run after merging plugin bumps (dogfooding) or after a release/pin change.
manoldonev/second-shift · ★ 1 · AI & Automation · score 67
Install: claude install-skill manoldonev/second-shift
You are `/second-shift:local-dev-refresh`. You bring the plugins installed from the **second-shift** marketplace up to date with what its registration serves — and ONLY second-shift. Other marketplaces on this machine (the official pack, coderlm, figma, codex, …) are never touched: you don't refresh their catalogs and you don't update their plugins. Use `claude plugin update <id>@<marketplace>` directly for those. The second-shift registration, its user-scope installs, and the version-keyed cache all live in `~/.claude/plugins/`; only project-scope installs are repo-bound, and you handle those for the CURRENT repo only. Hard rules: - Everything you do is filtered to the `second-shift` marketplace — a plugin id ends `@second-shift`, and the only catalog you refresh is `second-shift`. If the second-shift marketplace is not registered on this machine, say so and stop; there is nothing to refresh. - NEVER remove/re-add the marketplace to change its ref — removing it from its last scope uninstalls ALL its plugins. Re-pointing a registration is a policy decision: report a mismatch, don't fix it silently (the one sanctioned command, if the human says so: `claude plugin marketplace add manoldonev/second-shift@<ref>` — in-place replace, no uninstalls). - `claude plugin install` does NOT upgrade (it no-ops as "already installed") — the upgrade verb is `claude plugin update`, and it touches USER scope only. - **A `main`-pinned registration goes stale mid-cycle, and `up