homebrew-setup
Skill0 starsChanged 3 months agoMITView on GitHub
Installs and configures Homebrew on macOS - official installer, shellenv line in ~/.zprofile, brew doctor, and the Brewfile/brew bundle workflow with mas. Use for "install homebrew", "brew command not found", "brew doctor problems", "set up a Brewfile", "brew bundle dump/restore". Not for choosing which tools or apps to install, upgrade runs, or Xcode Command Line Tools.
- Installs packages
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-skillSkill
- publish-repoSkill
- ai-dev-toolsSkill
- cloud-dev-setupSkill
- dev-cli-toolsSkill
- docker-on-macSkill
- dotfiles-setupSkill
- editor-setupSkill
- git-ssh-identitySkill
- language-runtimesSkill
- mac-dev-appsSkill
- mac-maintenanceSkill
- macos-defaultsSkill
- macos-dev-setupSkill
- macos-security-baselineSkill
- macos-system-prepSkill
- mobile-dev-setupSkill
- web-dev-setupSkill
- zsh-setupSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 106
Default file resolution when --file is omitted: ./Brewfile, or with --global: ~/.Brewfile (and XDG variants).
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Homebrew Setup
Installs Homebrew correctly (right prefix, PATH wired for every future
shell), verifies it, and establishes the Brewfile workflow that makes the
machine reproducible. This skill owns the brew line in ~/.zprofile and
the Brewfile regeneration workflow — other skills install packages but never
rewrite those.
When NOT to use
- Which CLI tools to install →
dev-cli-tools; GUI apps →mac-dev-apps - Routine
brew update/upgrade/cleanupruns →mac-maintenance - Xcode CLT missing →
macos-system-prep(prerequisite of this skill) - Local databases as services →
web-dev-setup
Prerequisites
xcode-select -p must resolve. If not, stop and run macos-system-prep
first — and never let the Homebrew installer and the CLT GUI installer run
at the same time.
Safety rails
- The installer script asks for the admin password and prints what it will do — let the user see that; don't suppress output.
- Append to
~/.zprofileonly with a grep-guard (idempotent; no duplicate lines on re-run). brew bundle dumprefuses an existing Brewfile;--forceoverwrites it andbrew bundle cleanup --forceuninstalls everything not listed — update via temp-candidate + diff + user approval, never a blind--force.- Analytics: surface
brew analytics offas a choice; don't decide silently.
Workflow
1. Detect
command -v brew && brew --prefix && brew --versionAlready installed → skip to step 3. Prefix sanity: /opt/homebrew on Apple
Silicon, /usr/local on Intel. An /usr/local brew on an arm64 machine is
a Rosetta-era install — flag it instead of piling a second install on top.
2. Install
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/HEAD/install.sh)"Then wire PATH for future login shells (macOS terminal tabs are login shells, so this covers normal use; non-login contexts inherit PATH from their parent):
BREW_BIN=/opt/homebrew/bin/brew; [ -x "$BREW_BIN" ] || BREW_BIN=/usr/local/bin/brew
# Inspect any existing shellenv line first - a stale /usr/local line on an
# arm64 machine must be REPLACED (backup first), not treated as "already done":
grep -n 'shellenv' ~/.zprofile 2>/dev/null
# If none (or after removing a stale one):
grep -q "${BREW_BIN} shellenv" ~/.zprofile 2>/dev/null || {
echo >> ~/.zprofile
echo "eval \"\$(${BREW_BIN} shellenv)\"" >> ~/.zprofile
}
eval "$(${BREW_BIN} shellenv)"3. Verify
brew --version
brew --prefix # matches architecture
brew doctor # "ready to brew" - warnings are advisory, errors are notConfirm in a new terminal that brew resolves (that's the whole point
of the .zprofile line). Optionally: brew analytics off.
4. Brewfile workflow (reproducibility)
brew bundle is built into brew (no tap needed). Core loop:
# Snapshot current machine -> Brewfile. Note: dump REFUSES an existing file
# (it does not prompt). To update an existing Brewfile safely: dump to a
# temp candidate, diff, then replace only after the user approves.
brew bundle dump --describe --file=/tmp/Brewfile.candidate
diff -u ~/Brewfile /tmp/Brewfile.candidate # show the user; then move over ~/Brewfile
# (First-ever snapshot with no existing file: dump straight to ~/Brewfile.)
# Restore/converge a machine from the file (installs AND upgrades listed items)
brew bundle install --file=~/Brewfile
# Check without changing anything (exit code for scripts)
brew bundle check --file=~/Brewfile
# List what's installed but NOT in the file (review before any cleanup --force)
brew bundle cleanup --file=~/BrewfileDefault file resolution when --file is omitted: ./Brewfile, or with
--global: ~/.Brewfile (and XDG variants). Brewfile entries cover brew
(formulae), cask, tap, mas "App", id: N (needs brew install mas and
an App Store sign-in), and vscode "publisher.extension".
Recommend: keep the Brewfile in a dotfiles repo (see dotfiles-setup) and
re-dump after intentional installs. This file is infrastructure — the
10-minute path from a blank Mac back to all your tools.
5. Verify script
sh "${CLAUDE_SKILL_DIR}/scripts/check.sh"Details that age (current version, support tiers, cask renames): references/homebrew-facts.md.
Output spec
Done means: brew doctor passes in a fresh shell, the shellenv line exists
exactly once in ~/.zprofile, and (if requested) a Brewfile exists and
brew bundle check passes. Report actual outputs.
Gotchas
brew install dockerinstalls the CLI formula only (no engine); the Docker Desktop cask isdocker-desktop(renamed fromdockermid-2025; the old token still resolves). Container-runtime choice →docker-on-mac.mascannot sign in to the App Store (mas signinis gone) — the user signs into the App Store app once, thenmas install <id>works.- Migrated-from-Intel Macs often carry a
/usr/localbrew alongside/opt/homebrew;type -a brewexposes it. One brew per architecture — don't maintain both. - Homebrew requires macOS Sonoma 14+ (current tiers) and drops Intel to best-effort from late 2026 — on older/Intel machines expect missing bottles and slow source builds.
brew bundle installalso upgrades listed packages by default; useHOMEBREW_BUNDLE_NO_UPGRADE=1when that's unwanted.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

