brainstorming
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
homebrew-formula-maintenanceHomebrew formula maintenance workflows for Python CLIs and taps, including version bumps, SHA/resource updates, testing, audits, and releases.
Independent GitHub snapshot · Automated classification · Original documentation governs
name: homebrew-formula-maintenance description: Homebrew formula maintenance workflows for Python CLIs and taps, including version bumps, SHA/resource updates, testing, audits, and releases. user-invocable: false disable-model-invocation: true version: 1.0.0 category: toolchain author: Claude MPM Team license: MIT progressive_disclosure: entry_point: summary: "Maintain Homebrew Python formulas: bump version/sha, refresh resources, test install, audit/style, and push tap updates." when_to_use: "Updating Homebrew tap formulas for Python CLIs, syncing PyPI releases, or automating tap updates in CI." quick_start: "1. Verify PyPI release exists 2. Update url+sha in Formula 3. Regenerate resources if needed 4. brew install --build-from-source + brew test + brew audit" tags:
Use this workflow to keep Homebrew formulas in sync with PyPI releases for Python CLIs. The pattern in your taps is: update version + sha, refresh resource blocks when needed, run brew install/test/audit, then push the tap update (manually or via CI).
url and sha256 in the formula.resource stanzas if the formula uses virtualenv_install_with_resources.brew install --build-from-source + brew test + brew audit --strict.homebrew-claude-mpm/scripts/update_formula.sh <version>
homebrew-claude-mpm/scripts/generate_resources.py
resource blocks from PyPI.homebrew-claude-mpm/scripts/test_formula.sh
mcp-vector-search/scripts/update_homebrew_formula.py
--dry-run, --version, --tap-repo-path and HOMEBREW_TAP_TOKEN.curl -s https://pypi.org/pypi/<package>/<version>/json.url and sha256 in Formula/<name>.rb.If the formula uses Language::Python::Virtualenv and virtualenv_install_with_resources:
resource stanzas after dependency changes.generate_resources.py or equivalent; review output before pasting.Run these in the tap repo:
brew install --build-from-source ./Formula/<name>.rb
brew test <name>
brew audit --strict ./Formula/<name>.rb
brew style ./Formula/<name>.rb
CHANGELOG.md if the tap repo tracks releases.include Language::Python::Virtualenvvirtualenv_install_with_resourcesresource blocks to pin dependenciestest do uses CLI commands like --version and subcommandspip install -v buildpathbin.install_symlink for CLI entrypointtest do uses --version and --helpYour GitHub Actions workflow for Homebrew updates follows this flow:
workflow_run after CI succeeds.scripts/update_homebrew_formula.py.HOMEBREW_TAP_TOKEN (and optional HOMEBREW_TAP_REPO).python@x.y dependency is present.python@x.y dependency and virtualenv_install_with_resources usage.toolchains/universal/infrastructure/github-actionstoolchains/universal/infrastructure/docker