add-homebrew-tap

Creates Homebrew cask and formula templates with release automation for prebuilt CLI binaries.

10|1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/catalystctl/catcode --skill add-homebrew-tap-catalystctl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-homebrew-tap
Source: https://github.com/catalystctl/catcode/tree/main/.catalyst-code/skills/add-homebrew-tap
Command: npx skills add https://github.com/catalystctl/catcode --skill add-homebrew-tap-catalystctl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Distributing a prebuilt CLI binary through Homebrew requires correctly structured cask and formula files, SHA256 handling per architecture, and a tap repository that stays in sync with GitHub Releases. Doing this by hand is error-prone, especially when release workflows misname versioned assets. ## Core Features & Use Cases - Cask and Formula Templates: Generates placeholder-based Ruby templates (@@VERSION@@, @@SHA256_ARM@@, @@SHA256_INTEL@@) for both brew install and brew install --cask distribution. - Render Script and Release Workflow: Produces a render.sh script plus a GitHub Actions workflow gated to v* tags that downloads release assets, computes hashes, and pushes to a homebrew-<tool> tap repo. - Version Consistency Fix: Detects and fixes release workflows that name assets with commit SHAs instead of semver on version tags, which breaks both install.sh and Homebrew. - Use Case: A project ships per-arch macOS binaries and a .dmg on GitHub Releases; this Skill wires up the full tap so a v* tag release auto-publishes both the cask and formula. ## Quick Start Set up Homebrew distribution with both a cask and a formula for my CLI that publishes prebuilt binaries to GitHub Releases.

Frequently Asked Questions about add-homebrew-tap

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I distribute a CLI binary via Homebrew?

Create a homebrew-<tool> tap repository containing a formula that downloads your prebuilt binary from GitHub Releases with per-arch URLs and SHA256 hashes. A release workflow can automate rendering and pushing the formula on each version tag.

Should I use a Homebrew cask or formula for a CLI tool?

A CLI binary without a .app bundle is idiomatic as a formula, but a cask also works in a personal tap via the binary stanza. Shipping both in one tap has no name conflict since unqualified brew install resolves to the formula.

Can a web service or app with a background service be a Homebrew cask?

No. Web frontends requiring a runtime, background service, and configuration cannot be packaged as a cask or formula. Instead, point users to a one-line installer script through the caveats block in the cask or formula.

Why does brew upgrade not work with my tap releases?

This happens when release assets are named with commit SHAs instead of semver versions, since SHA versions are not monotonic and brew cannot rank them. Gate the tap workflow to v* tags and ensure assets use semver names derived from GITHUB_REF_NAME.

What manual setup is required before the Homebrew tap automation works?

Create an empty public homebrew-<tool> repository and add a HOMEBREW_TAP_TOKEN personal access token with contents-write permission as a repository secret. After that, publishing a v* tag release automatically populates the tap.