🎯

homebrew

🎯Skill
g1joshi/agent-skills1 Installs9Last Updated Feb 10, 2026

Installation

$npx skills add g1joshi/agent-skills --skill homebrew

Run it in a terminal; it asks which AI coding tools to install it for (Claude Code, Codex, Cursor and more).

Uses skills.sh Β· Node.js 22.20+

After installing

Ask for related work and the agent uses it on its own, or call it yourself.

Run it (Claude Code)/homebrew
Install by hand

Copy the whole skill folder from GitHub to the place below. Copying only SKILL.md can leave out files the skill uses.

Open the skill folder β†’
  • This project .claude/skills/homebrew/
  • All projects ~/.claude/skills/homebrew/

These paths are for Claude Code. For other tools, the command above puts it in the right place.

Expert Homebrew package manager assistance covering formulae, casks, taps, services, and bundle files (Brewfile). Use when managing developer tools and macOS/Linux system dependencies.

Homebrew

Homebrew is the premier package manager for macOS and Linux, simplifying the installation and declarative management (via Brewfiles) of developer tools and libraries.

When to Use

  • macOS & Linux Developer Environment Setup: Installing command-line utilities, programming runtimes, and GUI applications.
  • Automating Workstation Provisioning with Brewfile: Declaring team development environments using brew bundle.
  • Authoring Custom Enterprise Formulae & Taps: Distributing internal CLI tools and binaries via private GitHub taps.
  • System Service Management: Managing background daemons (PostgreSQL, Redis, Nginx) using brew services.

Quick Start

# Install wget
brew install wget

# Install VS Code (Cask)
brew install --cask visual-studio-code

Core Concepts

Declarative Workstation Setup with Brewfile

Specifying developer dependencies for automated bootstrapping:

# Brewfile in repository root
tap "homebrew/bundle"
tap "hashicorp/tap"

# CLI Utilities & Runtimes
brew "git"
brew "zsh"
brew "node@22"
brew "python@3.12"
brew "rust"
brew "hashicorp/tap/terraform"
brew "gh"
brew "jq"

# Background Development Daemons
brew "postgresql@16", restart_service: true
brew "redis", restart_service: true

# GUI Applications (macOS Casks)
cask "visual-studio-code"
cask "docker"
cask "raycast"
cask "postman"
# Install all dependencies declared in Brewfile
brew bundle --file=./Brewfile

# Check for unmanaged or missing dependencies
brew bundle check

Authoring a Custom Formula in Ruby

Packaging a CLI tool for distribution via a custom tap:

# Formula/mytool.rb
class Mytool < Formula
  desc "Cloud deployment and verification CLI for enterprise platforms"
  homepage "https://github.com/my-org/mytool"
  url "https://github.com/my-org/mytool/releases/download/v1.0.0/mytool-1.0.0.tar.gz"
  sha256 "a1b2c3d4e5f60718293a4b5c6d7e8f90123456789abcdef0123456789abcdef0"
  license "MIT"

  depends_on "node@22"

  def install
    bin.install "bin/mytool"
    prefix.install "lib"
  end

  test do
    assert_match "mytool version 1.0.0", shell_output("#{bin}/mytool --version")
  end
end

Managing Background Services with brew services

Starting and monitoring local services:

# Start PostgreSQL service in background
brew services start postgresql@16

# Inspect running services status
brew services list

# Stop service
brew services stop postgresql@16

Common Patterns

Reproducible Developer Machine Setup with Brewfile

Problem: Onboarding new developers requires manually running dozens of brew install commands.

Solution: Define team developer tooling in a version-controlled Brewfile:

# Brewfile
tap "homebrew/bundle"

brew "git"
brew "node@20"
brew "postgresql@16", restart_service: true
brew "gh"

cask "docker"
cask "visual-studio-code"

Execute setup: brew bundle install

Best Practices

Do:

  • Maintain a Brewfile in dotfiles or team repos to make onboarding new engineers reproducible.
  • Run brew update and brew upgrade regularly to receive security patches and updated formulae.
  • Pin major versions of runtimes (brew "node@22", brew "postgresql@16") to avoid breaking updates.
  • Run brew doctor if build links or dependency paths become corrupted.

Don't:

  • Run sudo brew ...; Homebrew is explicitly designed to run as an unprivileged user.
  • Modify files directly inside /opt/homebrew or /usr/local/Homebrew manually.
  • Leave orphaned dependencies; clean up disk space periodically with brew cleanup.

Troubleshooting

ErrorCauseSolution
Error: Your CLT does not support macOS ...Outdated Xcode Command Line Tools.Reinstall tools: xcode-select --install and run brew doctor.
Error: Formula '...' is not installedAttempting to link or start service for uninstalled formula.Install formula first: brew install <formula>.
brew doctor reporting permission warnings in /opt/homebrewFiles in Homebrew prefix owned by root instead of current user.Fix ownership: sudo chown -R $(whoami) $(brew --prefix)/*.

References

More from this repository10