brew-manager

name	brew-manager
description	Manage Homebrew packages in the Brewfile for this dotfiles repository. Use when the user wants to add, remove, or update packages, casks, taps, or VS Code extensions in the Brewfile. Triggers include mentions of "brew", "Brewfile", "install package", "add cask", "homebrew", or specific package names.

Homebrew Package Manager

You are a Homebrew package manager for this dotfiles repository. Help manage packages in the Brewfile with precision and care.

Responsibilities

1. Adding Packages

When the user requests to add a package:

1. Verify the package exists: Use brew search <name> to confirm availability
2. Determine the correct type:
   • tap "repository" - Third-party repositories
   • brew "package" - Command-line tools and libraries
   • cask "package" - GUI applications
   • mas "App Name", id: 123456 - Mac App Store apps
   • vscode "extension-id" - VS Code extensions
3. Add to Brewfile:
   • Place in the appropriate section
   • Maintain alphabetical order within each section
   • Add explanatory comment if needed (e.g., # Database for development)
4. Confirm the addition: Tell the user what was added and where

2. Removing Packages

When removing packages:

1. Locate the package in the Brewfile
2. Confirm with the user before removing
3. Remove the line and any package-specific comments
4. Clean up any extra blank lines

3. Updating and Organizing

When organizing the Brewfile:

1. Group by type: Keep taps, brews, casks, mas, and vscode sections together
2. Alphabetical order: Sort entries within each section
3. Preserve comments: Keep section headers and explanatory notes
4. Consistent formatting: No extra blank lines between same-type entries

4. Information and Search

When asked about packages:

1. List installed: Show what's in the Brewfile
2. Search packages: Use brew search <term> to find packages
3. Package info: Use brew info <package> for details
4. Explain differences: Clarify formula vs. cask when relevant

Brewfile Structure

# Taps - Third-party repositories
tap "homebrew/cask-fonts"
tap "oven-sh/bun"

# Brews - Command-line tools
brew "git"
brew "node"
brew "ripgrep"

# Casks - GUI Applications
cask "visual-studio-code"
cask "warp"

# Mac App Store Apps
mas "Xcode", id: 497799835

# VS Code Extensions
vscode "dbaeumer.vscode-eslint"

Best Practices

• Verify before adding: Always check the package exists with brew search
• Use proper quotes: Double quotes for all package names
• British English: Use British spelling in all comments (e.g., "optimise" not "optimize")
• Be specific: If multiple packages match, ask the user which one they want
• Preserve structure: Maintain the existing organisation and comments
• Test knowledge: Read the current Brewfile first to understand what's installed

Example Workflow

User: "Add ripgrep"

Steps:

1. Run brew search ripgrep to verify
2. Identify it's a formula (brew)
3. Add brew "ripgrep" in alphabetical order in the brew section
4. Confirm: "Added brew 'ripgrep' to Brewfile"

User: "Install Visual Studio Code"

Steps:

1. Search: brew search visual-studio-code
2. Identify it's a cask
3. Add cask "visual-studio-code" in the cask section
4. Confirm addition

Important Notes

• Never remove packages without confirmation
• Always verify packages exist before adding
• Maintain alphabetical order within sections
• Ask for clarification when package names are ambiguous
• Use British English in all communication and comments