joshgachnang/brewery

Turn a one-line request into a merge-ready, CI-green pull request, asking you only what matters.
brewery is a set of agent skills (for Claude Code, Cursor, and Codex) plus a brewery CLI
that runs every step as its own agent process.
mermaid
flowchart LR
R([request]) --> D[distill write the plan] --> C[cut attack the plan] --> S{{you sign off}}
S --> B[barrel build every task tests-first] --> F[finish CI green, bots answered] --> M([merge])
B -. stuck .-> G{{you answer a gate}} -.-> B
bash
git clone https://github.com/joshgachnang/brewery ~/src/brewery && ~/src/brewery/bin/install
mkdir -p ~/.config/brewery && echo '{"notify":{"ntfyUrl":"https://ntfy.sh/ "}}' > ~/.config/brewery/config.json
cd ~/src/your-repo && brewery pour "add a --json flag to the status command" # a repo with a GitHub remote
Set your own ntfy topic first: the default sends "brewery needs you" pings to the author.
Or let an agent do the whole setup: "Follow plugins/brewery/skills/install/SKILL.md from
github.com/joshgachnang/brewery", or /brewery:install once the plugin is in.
## Install
One line each. The install skill does all of this, checks before every change, and
reports what it skipped.
Plugin (the skills, in interactive sessions): /plugin marketplace add joshgachnang/brewery, then /plugin install brewery@brewery.
CLI (unattended runs): clone, then bin/install, then brewery agents to check it.
Your config: set your own ntfy topic in ~/.config/brewery/config.json.
A repo: brewery init-docs, plus the testing and user guide conventions tables.
Prerequisites
| Tool | Why |
| git | everything |
| gh, authenticated | PRs, CI waits, issues, approvals |
| Bun | the CLI (bin/install looks in ~/.bun/bin, then PATH) |
| Claude Code (claude) | default agent for every stage |
| Codex (codex) | optional second opinion on cut and branch review |
| Cursor agent (agent) | optional cursor profile |
Plugin: Claude Code, Cursor, Codex
Claude Code
/plugin marketplace add joshgachnang/brewery
/plugin install brewery@brewery
or declare it in a settings file:
json
"extraKnownMarketplaces": {
"brewery": {"source": {"source": "github", "repo": "joshgachnang/brewery"}}
},
"enabledPlugins": {"brewery@brewery": true}
Skills are namespaced by plugin: /brewery:distill, /brewery:barrel.
Cursor
Team marketplace: Dashboard → Plugins & MCPs → Team Marketplaces → Add Marketplace →
Import from Repo, and paste https://github.com/joshgachnang/brewery.
Local: link the plugin directory into ~/.cursor/plugins/local/, e.g.
ln -s ~/src/brewery/plugins/brewery ~/.cursor/plugins/local/brewery, then
Developer: Reload Window.
Codex
codex plugin marketplace add joshgachnang/brewery
codex plugin add brewery@brewery
Skills show up as brewery:distill, brewery:harvest, and so on; mention one with $ in
the composer to invoke it.
CLI
bash
~/src/brewery/bin/install # bun install, and links ~/bin/brewery to cli/src/cli.ts
brewery agents # which agents are available, and how each stage routes
Run from the checkout, the CLI finds its skills in plugins/brewery/skills. A repo that
vendors its own ( /.claude/skills/distill) uses those, and BREWERYSKILLSDIR
overrides both. bun run compile in cli/ builds a standalone binary, which falls back to