homebrew-tap-merge
Skill4 starsChanged 3 months agoApache-2.0View on GitHub
Verify and merge the bot PR that release.yml auto-opens on homebrew-tap for a new agent-assembly release. Use when a bot/aasm-<version> PR is open on the Homebrew tap and needs sha256 cross-verification against the upstream SHA256SUMS, a stale-master server-side rebase, or the AAASM-2871 macOS-CI tap-trust workaround before it can be merged.
- Deletes or force-pushes
- Installs packages
- Commits and pushes
In this repository21 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- adr-governanceSkill
- credential-operationsSkill
- documentation-experienceSkill
- engineering-loopSkill
- governance-doctorSkill
- jira-deliverySkill
- product-validationSkill
- public-release-reconcileSkill
- release-assuranceSkill
- release-docs-syncSkill
- release-evidence-finalizeSkill
- release-qa-gateSkill
- release-security-gateSkill
- release-tag-cutSkill
- release-validate-channelsSkill
- repo-bootstrapSkill
- repo-scaffoldSkill
- rust-developmentSkill
- shell-developmentSkill
- terraform-developmentSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 1 is distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 10
After each agent-assembly release, release.yml's update-homebrew-tap job opens a bot/aasm-<version> PR on ai-agent-assembly/homebrew-tap …
- Very specific: line 76
If mergeStateStatus is BEHIND (stale master), trigger a server-side rebase (no local force-push):
- Distinctive: line 85
Wait for CI to re-run, then re-evaluate.
- Very specific: line 87
If the PR is up to date, surface the failure log with gh run view --repo ai-agent-assembly/homebrew-tap --job <id> --log-failed.
- Very specific: line 121
Follow up with /release-validate-channels v<version> (or re-run scripts/check-release.sh v<version>) and confirm the Homebrew row goes …
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
SKILL.md — homebrew-tap-merge
Purpose
After each agent-assembly release, release.yml's update-homebrew-tap job
opens a bot/aasm-<version> PR on ai-agent-assembly/homebrew-tap
that bumps Formula/aasm.rb (version line + 4 SHA256 sums). This skill owns the
verify-and-merge flow for that PR so brew install aasm picks up the release.
The skill lives in agent-assembly because the tap repo has no Jira component;
it is logically owned by the upstream that publishes to it.
When to use
Invoke when release.yml's update-homebrew-tap job has finished and a
bot/aasm-<version> PR is open on ai-agent-assembly/homebrew-tap,
and the operator (or release-watch) wants to verify the bot diff and merge it.
When NOT to use
- Tap PR not yet open — wait for
release.yml; do not hand-open a PR. - Tap PR has manual edits beyond the bot's diff — anything outside the version line + 4 sha256 lines is out of scope. Escalate; do not auto-merge a hand-edited formula.
- AAASM-2871 (Homebrew/brew#22719) is patched upstream — if the tap's
brew install + testworkflow no longer needsHOMEBREW_NO_REQUIRE_TAP_TRUST=1, the step-3 rebase shortcut may no longer be required; re-evaluate.
How to use
/homebrew-tap-merge <PR_NUMBER>Example: /homebrew-tap-merge 16. Resolve the PR number with
gh pr list --repo ai-agent-assembly/homebrew-tap --state open. The
matching upstream agent-assembly release must already be published with its
SHA256SUMS asset attached.
Executable plan
1. Verify PR scope
gh pr view <n> --repo ai-agent-assembly/homebrew-tap \
--json files,additions,deletionsExpected: single file Formula/aasm.rb, ~5 additions and ~5 deletions. Reject
anything broader as out-of-scope.
2. Cross-verify all 4 sha256 lines vs upstream
.claude/skills/homebrew-tap-merge/scripts/verify-tap-sha256.sh <tag> [<pr>]
# e.g. .claude/skills/homebrew-tap-merge/scripts/verify-tap-sha256.sh v0.0.1-alpha.9 16Exits 0 iff all 4 sha256s match the upstream SHA256SUMS asset (one per
platform: aarch64-apple-darwin, x86_64-apple-darwin,
aarch64-unknown-linux-gnu, x86_64-unknown-linux-gnu). Non-zero exit prints a
mismatch table — escalate; do not merge.
3. Handle red brew install + test (macOS) check
gh pr view <n> --repo ai-agent-assembly/homebrew-tap \
--json baseRefOid,mergeable,mergeStateStatusIf
mergeStateStatusisBEHIND(stale master), trigger a server-side rebase (no local force-push):gh api -X PUT \ /repos/ai-agent-assembly/homebrew-tap/pulls/<n>/update-branch \ -f update_method=rebaseWait for CI to re-run, then re-evaluate. See the AAASM-2871 note below.
- If the PR is up to date, surface the failure log with
gh run view --repo ai-agent-assembly/homebrew-tap --job <id> --log-failed.
4. Merge
Once CI is green and sha256s are verified:
gh pr merge <n> --repo ai-agent-assembly/homebrew-tap --squashAAASM-2871 quirk (live until Homebrew/brew#22719 ships)
The tap's brew install + test (macOS) check needs
HOMEBREW_NO_REQUIRE_TAP_TRUST=1 in the workflow env. A bot PR on stale master
predates that fix and fails with a silent sandbox-exec SIGKILL — the step-3
server-side rebase pulls in the env and clears it. Limit to one rebase attempt
before escalating. Background: memory entry
project_homebrew_tap_sandbox_kills_install.
Do NOT (auto-handled or forbidden)
- Opening the bot PR — owned by
release.yml'supdate-homebrew-tapjob. - Editing
Formula/aasm.rbby hand — never. A mismatched sha256 means a real upstream release-artifact problem; escalate, do not "fix" the formula. - Local
git push --forceto the bot branch — use the server-sideupdate-branchAPI (step 3); force-push breaks the bot's audit trail. - Merging past a red
brew install + testcheck — users hit the same failure onbrew install.
Post-conditions
- Tap
master'sFormula/aasm.rbhas the new version + 4 verified sha256s. - The bot PR is closed and merged (squash), not just approved.
- Follow up with
/release-validate-channels v<version>(or re-runscripts/check-release.sh v<version>) and confirm the Homebrew row goes green.
Detailed references
- EXAMPLES.md — full worked alpha-9 walk-through of all 4 steps, including the stale-master rebase path and the verified sha256 table.
scripts/verify-tap-sha256.sh— the step-2 cross-verification helper.docs/release/RUNBOOK.md§ "Manual gate — merge the Homebrew tap PR"..github/workflows/release.yml§update-homebrew-tapjob (PR producer).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

