plugin-update

Brewcode Plugin Update

First output: the PLAN block below, as plain text, before any tool call.

Updates every installed claude-brewcode plugin and mod at its own scope without asking what to update, offers what is missing in one question, then prints one report: versions before -> after, what changed for you, numbered next steps. /reload-plugins and the /plugin UI are user handoffs, never tool actions.

Prompt contract

$ARGUMENTS is one free-form RU/EN prompt; the mode token may sit anywhere in it.

1. Mode: an explicit mode token wins outright; else the most distinct whole-word keyword hits (table below). Tie with check -> check; update vs all -> the keyword that comes first. No hit or empty -> update.
2. Scope: always every installed claude-brewcode plugin and mod, in every scope; the prompt never narrows the update (user ruling: updating is automatic). A missing plugin or mod named in the prompt is still only an offer: the Phase 3 question (update) or all.
3. Ask: at most ONE AskUserQuestion per run, at most 2 questions, only in update and only when Phase 2 lists offers; after the PLAN block, before the first change. The update itself is never asked about. check asks nothing; all takes every offer without asking (the word is consent).

Your reply starts with this block, filled from the prompt alone, then Phase 0 runs. Print it once, in every mode, check included (labels and plan values English, INPUT verbatim). A block only in your thinking or only inside a tool call does not count:

PLAN — brewtools:plugin-update
INPUT:  <arguments verbatim, or "(empty)">
MODE:   <resolved> — <explicit | matched keyword: X | default>
SCOPE:  every installed claude-brewcode plugin and mod, every scope; missing ones <update: one question | all: installed | check: listed>
DO:     <2-5 imperative bullets, in phase order>
RESULT: <what the user ends up holding>

Modes