fix(skills): point gog brew install at homebrew-core gogcli (#95017)#95019
Conversation
|
Codex review: needs maintainer review before merge. Reviewed June 20, 2026, 6:07 PM ET / 22:07 UTC. Summary PR surface: Docs 0. Total 0 across 1 file. Reproducibility: yes. Source inspection shows current main passes the gog metadata formula through to Review metrics: 1 noteworthy metric.
Root-cause cluster Members:
Proposal only: this assessment does not dispatch repair, suppress jobs, mutate sibling items, close, or merge anything. Merge readiness Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch. Rank-up moves:
Risk before merge
Maintainer options:
Next step before merge
Security Review detailsBest possible solution: Merge this focused metadata update after normal maintainer checks, then let the linked issue close once main points gog at the Homebrew core formula. Do we have a high-confidence way to reproduce the issue? Yes. Source inspection shows current main passes the gog metadata formula through to Is this the best way to solve the issue? Yes. Updating the existing gog skill metadata is the narrowest maintainable fix because the parser and installer already support safe Homebrew core formula names without adding fallback logic. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning high; reviewed against f18ff7551edc. Label changesLabel justifications:
Evidence reviewedPR surface: Docs 0. Total 0 across 1 file. View PR surface stats
What I checked:
Likely related people:
What the crustacean ranks mean
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics. How this review workflow works
|
976ce22 to
a4f489c
Compare
|
Merged via squash.
Thanks @ZengWen-DT! |
…#95017) (openclaw#95019) Merged via squash. Prepared head SHA: a4f489c Co-authored-by: ZengWen-DT <[email protected]> Co-authored-by: vincentkoc <[email protected]> Reviewed-by: @vincentkoc
Summary
Onboarding's skill-dependency installer fails to install the
gogskill because its bundled metadata points at a Homebrew formula that no longer exists in that tap:gogclihas since graduated to homebrew-core, and the formula was removed fromsteipete/tap. The installer buildsbrew install steipete/tap/gogcli, which now fails with:This PR points the
gogskill at the canonical core formulagogcli, so the install command becomesbrew install gogcli. Using the core formula (vs.openclaw/tap/gogcli) also avoids the third-party-tap trust prompt the reporter hit.Fixes #95017.
Scope note
Only
gog's formula graduated to core. The othersteipete/tap/*skills (songsee,camsnap,peekaboo,imsg, etc.) still resolve in that tap, so they are intentionally left unchanged — verifiedsteipete/tapstill serves those formulae and no longer servesgogcli.Verification
Real behavior proof
Behavior addressed:
gogskill dependency install during onboarding fails because metadata references the removedsteipete/tap/gogcliformula; switching to the homebrew-coregogcliformula makes the resolvedbrew install gogclicommand succeed against Homebrew core.Real environment tested: Linux (WSL2) checkout, live network. The dependency contract was checked directly against the live Homebrew formulae API and the
steipete/homebrew-tapgit repo, and the skill install-spec resolution was exercised through the real skill frontmatter parser and the real install-argv builder.Exact steps or command run after this patch:
Evidence after fix: Live output captured after this patch.
Homebrew core now owns
gogcli(matches the reporter's working manual install):The old tapped formula is gone, while sibling tap formulae still resolve (so only
gogneeds changing):Running the real frontmatter parser + install-argv builder against the patched
skills/gog/SKILL.md:Observed result after fix: The resolved install command for
gogis nowbrew install gogcli, which resolves against homebrew-core (HTTP 200 / formula present) instead of the removed, untrustedsteipete/tap/gogcli(HTTP 404), eliminating the onboarding install failure.What was not tested: A full end-to-end
openclaw onboardrun on a fresh VPS that performs the actualbrew install(no clean VPS + Homebrew sandbox available here). The failure and fix are fully determined by the resolvedbrew install <formula>argument and the live Homebrew formula availability shown above.Notes