plugin-update

Discovery. claude plugin list --json (CC 2.1.163+) returns id, version, scope, enabled, installPath, installedAt, lastUpdated, optional mcpServers, and projectPath on project/local rows only. version may be "unknown" for locally loaded plugins. Inside a session the call is prefixed with unset CLAUDECODE &&. If it errors, returns nothing or invalid JSON, scripts/discover-plugins.sh reads settings.json (CLAUDE_CONFIG_DIR, default ~/.claude) and walks the cache (CLAUDE_CODE_PLUGIN_CACHE_DIR, default <config dir>/plugins/cache/). If both fail, the inventory is reported unknown and nothing is offered, installed or updated. Ids ending @inline, @skills-dir or @synced are not marketplace installs and never update.

Update chain. --scope is always passed from the plugin’s own discovery row, because CLIs before 2.1.281 read an omitted scope as user and update the wrong instance:

claude plugin marketplace update claude-brewcode
claude plugin update <id> --scope <scope>
(cd "<projectPath>" && claude plugin update <id> --scope <scope>)

Every outdated plugin and mod gets one such command, for example brewcode@claude-brewcode or brewmod-placeholders@claude-brewcode. Project and local rows run from their own projectPath. A missing directory is reported as an orphan install with mkdir -p "<projectPath>" && cd "<projectPath>" && claude plugin uninstall <id> --scope <scope> as the removal command; its table cell is ⚪ orphan install, never a failure. all also updates rows from other marketplaces (a no-op when current); they show in the table only when their version changed. If the marketplace refresh fails, the skill reports it, reads the published versions over the web, and adds the marketplace before any install.

Prune. all only, once per installed scope in this order: user from the session directory, then each project and local scope from its own project directory. claude plugin prune --dry-run --scope <scope> lists the orphans, then claude plugin prune --scope <scope> -y removes exactly that list: typing all is the consent. A scope whose directory is gone is skipped (the orphan report covers it), another scope such as managed is reported as unsupported, and a CLI without prune skips the step with a notice. Prune removes only auto-installed dependencies nothing still requires. The -y is mandatory: the Bash tool has no TTY, and a bare prune removes nothing yet exits 0.

No delegation. The skill spawns nothing; discovery, the chain and the question run in the main conversation so you see every command.

Claude summarizes instead of running? Paste: “Execute every claude plugin ... command shown above using the Bash tool. Do not describe, run each command and show full output.”

Titles and status cells appear verbatim. N is the number updated or installed, M the installed components, K the failed ones, X the version still installed and Y the latest.

A scope other than user shows as (scope: path) after the name; a missing version shows as —; a changed version is bold.

What changed for you. The text comes from RELEASE-NOTES.md in the local marketplace clone, never from the network. The range runs from your lowest installed claude-brewcode version, excluded, to the highest latest, included. Per version it shows the bullets under What changed for you: at most 3 per version and 10 in total, newest first, with the rest counted as +N more. A Claude Code requirement line shows once, and only when Claude Code is below 2.1.301 or its version cannot be read; migration bullets come first, and technical sections never appear. A clone older than the latest version (check, or a failed marketplace refresh) shows a line saying so, with the release-notes link.

Next steps. Numbered at run time:

A plugin update does not replace files a setup already copied into a project, so the upgrade step runs in each project; Setup Status explains it.

In check mode with updates available, the first step is /brewtools:plugin-update, which applies the N updates.

Below the table. Each missing mod and plugin the run did not install is listed with its claude plugin install command. When a mod is missing and Claude Code is below 2.1.301 or unreadable, a line tells you to run claude update instead of listing a mod install command.

Below the report. The skill adds 🔴 <command>: <first error line> for each failed marketplace refresh, update, install, prune or prune preview, and one line per orphan install with its removal command. A report flagged degraded (a latest version unknown, or the after list unreadable) is still complete and printed in full. Auto-update stays a user switch (/plugin → Marketplaces → claude-brewcode): the skill never edits settings.json or known_marketplaces.json.

An explicit mode word wins. Otherwise the most distinct whole-word keyword decides; a tie with check resolves to check, and update against all resolves to the keyword that comes first.