claude-brewcode

Claude Code plugin suite -- four plugins for development, documentation, text utility, and visual workflows.

A regular Claude Code session hands a big task to one agent and loses sight of it. Brewcode splits work into bounded units, gives every spawn a six-field brief, and re-states the delegation rule on every prompt. Four plugins. 27 skills. 8 agents. 4 lifecycle hooks.

Full Documentation

Approaches -- every hook, agent and injection the suite installs, and who installs what.

Security: Code is scanned on every commit. No personal data is collected or transmitted.

🚀 Install in 30 seconds

Paste this prompt into any Claude Code session -- Claude will run the full install 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.

Already installed? Update with this prompt:

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 install/update, run /reload-plugins (or exit + claude to restart). For manual install steps see Installation below.

Plugin Suite

| Plugin | Purpose | Skills | Install | |--------|---------|--------|---------| | brewcode | Infinite task execution, quorum reviews, skill/agent creation, semantic search | 9 | claude plugin install brewcode@claude-brewcode | | brewdoc | Documentation tools: docsync, memory-sync generation, PDF conversion, publishing | 5 | claude plugin install brewdoc@claude-brewcode | | brewtools | Universal text utilities: token optimization, humanization, secrets scanning, plugin updates | 13 | claude plugin install brewtools@claude-brewcode | | brewui | UI/visual/creative tools (placeholder, currently empty) | 0 | claude plugin install brewui@claude-brewcode |

Installation

Marketplace (recommended)

Permanent installation through the Claude Code plugin system. Plugins load automatically with every session.

1. Add marketplace -- registers the plugin source:

claude plugin marketplace add https://github.com/kochetkov-ma/claude-brewcode

2. Install plugins -- copies plugins to local cache:

claude plugin install brewcode@claude-brewcode
claude plugin install brewdoc@claude-brewcode
claude plugin install brewtools@claude-brewcode
claude plugin install brewui@claude-brewcode

3. Reload plugins -- run /reload-plugins in Claude Code, or exit + claude to restart.

Already installed? Update

Use /brewtools:plugin-update inside Claude Code for the easiest path -- it runs all update commands and reloads automatically.

Or run manually:

claude plugin marketplace update claude-brewcode
claude plugin update brewcode@claude-brewcode
claude plugin update brewdoc@claude-brewcode
claude plugin update brewtools@claude-brewcode
claude plugin update brewui@claude-brewcode

After updating, run /reload-plugins (preferred) or exit + claude to restart.

Local directory (for development)

claude --plugin-dir ./brewcode --plugin-dir ./brewdoc --plugin-dir ./brewtools --plugin-dir ./brewui

Requirements

| Component | Version | Purpose | |-----------|---------|---------| | Claude Code CLI | latest | Plugin runtime | | Node.js | 20+ | Hook runtime | | macOS | 13+ | Supported OS |

macOS only. Linux and Windows support is planned for future releases.

Quick Start

brewcode -- infinite task execution

/brewtools:task-board-setup  # 1. Deploy the task board + a project-tailored /task-spec skill
/task-spec "Implement JWT authorization"  # 2. Research codebase + write the task spec and design
/brewcode:superreview-setup  # 3. Generate a project-tailored deep-review skill
/brewcode:setup-status       # anytime: what is installed, stale or missing in this project

Skills orchestrate, agents execute. Each spawn is a bounded unit with a six-field brief, and the forced-eval hook re-states the manager role and the split rule on every prompt, so work stays observable across compaction cycles.

brewdoc -- documentation tools

/brewdoc:docsync-setup                # Install doc-staleness tracking, then sync stale docs
/brewdoc:my-claude                    # Generate Claude Code installation docs
/brewdoc:memory-sync-setup            # Generate a project-tailored /memory-sync skill into the repo
/brewdoc:md-to-pdf ./docs/report.md   # Convert markdown to PDF
/brewdoc:publish "Hello world"        # Publish to brewpage.app -- returns public URL

brewtools -- text utilities

/brewtools:text-optimize CLAUDE.md         # Token-efficient optimization (52 rules)
/brewtools:text-human 3be67487             # Remove AI artifacts from a commit
/brewtools:secrets-scan                    # Scan for leaked credentials
/brewtools:plugin-update                   # Install or update the plugin suite

brewui -- visual tools

Placeholder plugin, currently empty. No commands yet -- coming soon.

How It Works

  /task-spec "..." --> parallel research agents + user Q&A --> per-task spec + design docs
        │
        v
  project agents from .claude/agents/ --> bounded units, fanned out in ONE message
        │
        v
  /brewcode:superreview-setup --> project-tailored deep-review skill

  every prompt: forced-eval (UserPromptSubmit) injects 3 lines --
    [ROLE]   scan agents, project .claude/agents/ first; domain expert exists -> delegate
    [SPLIT]  one agent for an hour = drift you cannot observe -> split and fan out
    [BRANCH] no branch chosen -> main; no explicit branch/PR -> take over the whole workspace

Delegation contract

Every skill that spawns subagents carries a ## Delegation section; every shipped agent carries a ## Scope guard. Both encode the same rule: one subagent = ONE bounded unit -- one deliverable, ~5 files, ~10 steps. Anything bigger is split into N tasks spawned in a single message.

Every spawn prompt carries six fields:

| Field | Content | |-------|---------| | GOAL | the overall task and why it exists -- the point beyond the file edit | | ROLE | what this agent owns; what it must NOT touch | | SCOPE | exact paths and commands in bounds, plus explicit out-of-bounds | | CONTEXT | what is already done, by whom, what runs in parallel | | CONSUMER | who or what uses the result next, and the shape it must fit | | DONE | acceptance criteria plus the exact report shape expected back |

Skills Reference

The -setup suffix marks a skill you run once to install a mechanism -- afterwards you use what it produced (a generated skill, a hook, an MCP server), not the skill itself. Recurring tools you invoke every day keep bare names. Every -setup skill shares one mode vocabulary: status | install | upgrade | enable | disable | uninstall | purge, and no argument means status when installed, install when not. The one exception is /brewcode:semble-setup, which always defaults to status so a bare invocation never triggers a machine-level package install. All eleven setups implement all seven verbs, via one of two mechanisms: a live config flag re-checked each 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 byte-identical (teams, superreview, task-board, think-short, memory-sync).

All 27 skills are user-invoked only. Every one carries user-invocable: true and disable-model-invocation: true in its frontmatter: the model never sees their descriptions and never auto-activates one. You type /plugin:skill, or nothing runs. This is a deliberate trade about context cost -- 27 model-visible descriptions would be a permanent tax on every request -- and these skills do not want auto-activation anyway: eleven of them write real files into your repo after asking you real questions, and the rest are tools you point at a scope you choose.

Brewcode (9 skills)

| Skill | Purpose | |-------|---------| | /brewcode:setup-status | Read-only cross-plugin dashboard: which setup skills are installed, stale, disabled, partial or missing here, plus the exact command to run for each. disabled outranks partial/stale, so a mechanism you turned off on purpose is never reported as broken. Runs nothing itself -- setups are interactive generators that spawn many subagents, and stacking several in one session degrades all of them | | /brewcode:superreview-setup | Generate a project-tailored deep-review skill: QUICK (default, intent-guard + mechanical gates) or EXTENDED (adds domain-expert fan-out, scope discipline, adversarial validation) depth, read from your prompt | | /brewcode:teams-setup | Create and manage dynamic teams of domain-specific agents -- every team also gets a fixed review-only intent-guard member (not counted in team size). Modes status/install/upgrade/enable/disable/uninstall/purge, each taking an optional team [name]; enable/disable park/unpark each roster member's agent file | | /brewcode:convention | Extract etalon classes, patterns, architecture into convention docs | | /brewcode:rules | Prompt-driven rules management: status, create, improve, review | | /brewcode:skills | Prompt-driven skill management: status, create, improve, sync, review | | /brewcode:agents | Prompt-driven agent