FAQ

If the skill is unavailable (very old install, plugin not yet installed, or Claude refuses to invoke it), paste the prompt below directly into the chat — Claude Code will execute every command for you:

Execute these commands in this Claude Code session, one by one, show full output for each, do not skip any, do not summarize:

1. claude plugin marketplace update claude-brewcode
2. claude plugin update brewcode@claude-brewcode
3. claude plugin update brewdoc@claude-brewcode
4. claude plugin update brewtools@claude-brewcode
5. claude plugin update brewui@claude-brewcode

After all commands succeed, run `/reload-plugins`. If `/reload-plugins` is unavailable, tell me to type `exit` and run `claude` again. Run the commands now.

After all commands succeed, run /reload-plugins inside your Claude Code session. If /reload-plugins is unavailable, type exit and run claude again.

If /brewtools:plugin-update is missing (very old install or partial install), use the Claude Code prompt below. It tells Claude to run the marketplace update + every plugin update for you, no skill required:

Execute these commands in this Claude Code session, one by one, show full output for each, do not skip any, do not summarize:

1. claude plugin marketplace update claude-brewcode
2. claude plugin update brewcode@claude-brewcode
3. claude plugin update brewdoc@claude-brewcode
4. claude plugin update brewtools@claude-brewcode
5. claude plugin update brewui@claude-brewcode

After all commands succeed, run `/reload-plugins`. If `/reload-plugins` is unavailable, tell me to type `exit` and run `claude` again. Run the commands now.

After Claude finishes, the /brewtools:plugin-update skill will be available for all future updates.

Paste the following prompt directly into the chat. The coercive phrasing is intentional — it prevents Claude from summarizing or skipping steps.

Execute these commands in this Claude Code session, one by one, show full output for each, do not skip any, do not summarize:

1. claude plugin marketplace update claude-brewcode
2. claude plugin update brewcode@claude-brewcode
3. claude plugin update brewdoc@claude-brewcode
4. claude plugin update brewtools@claude-brewcode
5. claude plugin update brewui@claude-brewcode

After all commands succeed, run `/reload-plugins`. If `/reload-plugins` is unavailable, tell me to type `exit` and run `claude` again. Run the commands now.

All four plugins install from the same claude-brewcode marketplace on GitHub — 28 skills and 8 agents in total.

A -setup suffix marks a skill that installs a mechanism into the project — agents, hooks, a generated skill, a board. After it runs you use the installed thing, not the skill. Skills without the suffix are recurring tools: running them repeatedly is the intended usage.

There are eleven -setup skills. They share one mode vocabulary — status | install | upgrade | enable | disable | uninstall | purge — and a bare invocation reports instead of installing once something is already there.

Skill-specific verbs come after the canonical set, never in place of it. All eleven setups implement all seven canonical verbs. Two mechanisms do the work: a live config flag that the reader re-checks on every invocation (semble, agent-deadline, agent-return, agent-router, manager, docsync), or entry-file parking, where the filename discovery keys on is renamed <name>.disabled with the body left byte-identical (teams, superreview, task-board, think-short, memory-sync).

Because that is the design. All 28 distributed skills carry both user-invocable: true and disable-model-invocation: true in their frontmatter. The model never sees their descriptions and never auto-activates one — a skill in this suite runs only when you type /plugin:skill.

This is a deliberate trade about context cost, not an oversight. Every skill whose description is model-visible spends tokens in every single request, forever, just to stay discoverable. Twenty-eight of them would be a permanent tax on the context window of every conversation, in exchange for auto-activation that these particular skills do not want anyway:

• The eleven -setup skills are interactive generators that write real files into your repo. Nothing should reach for one without you asking.
• The recurring tools (convention, rules, e2e, publish, text-optimize, secrets-scan, deploy, ssh) are things you run at a moment you choose, on a scope you choose.

The practical consequence: asking “can you sync my docs?” will not trigger /brewdoc:docsync-setup. Type the command. Tab completion after / lists everything that is installed.

Yes. Plugin changes only take effect after a reload.

Paste the prompt below into any Claude Code session — Claude will add the marketplace and install all four plugins for you:

Execute these commands in this Claude Code session, one by one, show full output for each, do not skip any, do not summarize:

1. claude plugin marketplace add https://github.com/kochetkov-ma/claude-brewcode
2. claude plugin install brewcode@claude-brewcode
3. claude plugin install brewdoc@claude-brewcode
4. claude plugin install brewtools@claude-brewcode
5. claude plugin install brewui@claude-brewcode

After all commands succeed, run `/reload-plugins`. If `/reload-plugins` is unavailable, tell me to type `exit` and run `claude` again. Run the commands now.

Plugins are stored locally after installation:

&#126;/.claude/plugins/cache/<marketplace>/<plugin>/<version>/

For example:

~/.claude/plugins/cache/claude-brewcode/brewcode/5.0.0/
~/.claude/plugins/cache/claude-brewcode/brewtools/5.0.0/

The marketplace metadata lives at:

~/.claude/plugins/marketplaces/

Run /brewtools:plugin-update inside a Claude Code session. It reports the installed and latest available version for each plugin and prompts you to update if a newer version exists.