lidge-jun/codexclaw / plugins/codexclaw/skills/dev-devops
cxc-dev-devops
VerifiedUse for infra, CI/CD, releases, repo policy, worktree cleanup and native desktop apps. Triggers: Dockerfile, K8s, IaC, SRE, Tauri, 스택 PR CI, 배포, 인프라, 쿠버네티스, 브랜치 정리, 브랜치 삭제, 워크트리 정리, 저장소 세팅, 브랜치 보호, 에이전트 PR, PR 정책, 데스크톱 앱, 메뉴 막대.
references/homebrew.md
View on GitHub# Homebrew — Formula & Cask Distribution
Last reviewed: 2026-06-21
Applies to: Homebrew Formulae, Homebrew Casks, taps, CLI package distribution on macOS/Linux
When to read: Updating or creating Homebrew distribution for a released artifact
Canonical owner: dev-devops Homebrew distribution guidance
---
## §1 Boundary
Homebrew is a downstream distribution channel. It does not replace upstream
package provenance.
Examples:
- npm package provenance still comes from npm Trusted Publishing.
- PyPI package provenance still comes from PyPI Trusted Publisher.
- Homebrew proof verifies that the tap installs the intended upstream artifact
and exposes the expected command/app behavior.
## §2 Formula vs Cask
| Use | Choose | Typical artifact |
|---|---|---|
| CLI built from source or bottled binary | Formula | tarball, source archive, binary release |
| macOS app bundle/pkg/dmg | Cask | `.app`, `.pkg`, `.dmg`, `.zip` |
| Both CLI and app exist | Usually Formula for CLI, Cask for app | Separate install paths and tests |
Ask for this classification before writing Homebrew guidance. Do not mix
Formula-only checks with Cask-only artifacts.
## §3 Formula Proof Bundle
Formula work should prove:
- stable tagged version or immutable release URL;
- URL and SHA256 match the intended artifact;
- dependencies are declared with `depends_on`;
- `test do` verifies the installed binary/library behavior;
- `brew test <formula>` passes;
- `brew audit <formula>` passes;
- `brew audit --strict --online <formula>` is used for public tap/core-quality
checks when network access is appropriate;
- version output matches the upstream release.
Minimal Formula shape:
```ruby
class ToolName < Formula
desc "Short user-facing description"
homepage "https://example.com/tool"
url "https://github.com/org/tool/archive/refs/tags/v1.2.3.tar.gz"
sha256 "..."
license "MIT"
def install
bin.install "tool"
end
test do
assert_match "1.2.3", shell_output("#{bin}/tool --version")
end
end
```
## §4 Cask Proof Bundle
Cask work should prove:
- `version`, `sha256`, `url`, and `name`/`desc` are correct;
- `livecheck` is present when feasible;
- `depends_on` captures macOS or architecture requirements;
- `app`, `binary`, `pkg`, or other artifact stanza matches the real install
shape;
- uninstall and `zap` behavior are documented for persistent user files;
- artifact trust is considered because vendor installers can write outside the
Caskroom;
- install and uninstall behavior is verified on macOS when the release claim
depends on it.
Minimal Cask shape:
```ruby
cask "tool-name" do
version "1.2.3"
sha256 "..."
url "https://example.com/tool-#{version}.dmg"
name "Tool Name"
desc "Short user-facing description"
homepage "https://example.com/tool"
app "Tool.app"
zap trash: [
"~/Library/Application Support/Tool",
"~/Library/Preferences/com.example.tool.plist",
]
end
```
## §5 Channel Alignment
For tools released through npm/PyPI and Homebrew, verify:
- upstream release exists before Homebrew update;
- Homebrew version matches upstream version;
- installed command reports the same version;
- Homebrew binary path does not shadow or conflict with the upstream package
manager path without documenting the expected precedence.
## §6 Common Anti-patterns
| Anti-pattern | Fix |
|---|---|
| Treating Homebrew as the canonical release | Publish canonical package first, update tap second |
| Missing `test do` in Formula | Add an install-time behavior check |
| No SHA256 or mutable artifact URL | Use immutable release artifact and checksum |
| Cask without uninstall/zap thinking | Document uninstall and persistent user data behavior |
| Claiming macOS install behavior from Linux CI only | Use macOS runner or direct macOS verification when local behavior matters |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |