Agent skill

CodexBar macOS Release

by steipete in steipete/CodexBar

Releases a signed, notarized CodexBar build: confirms the changelog, resolves signing credentials from 1Password, runs the release script in tmux, and updates the Sparkle appcast and Homebrew tap.

MITAuto-check passedDevOps & Cloud

Install CodexBar macOS Release

skills CLI
$ npx skills add steipete/CodexBar --skill release-codexbar -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install steipete/CodexBar release-codexbar --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/steipete/CodexBar.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/release-codexbar .claude/skills/release-codexbar && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
release-codexbar
GitHub stars
22k
Token cost
~1.5k tokens
SKILL.md length
442 words
Files
1
Skills in repo
3
Repo updated
First seen
Licence
MIT

At a glance

Releases a signed, notarized CodexBar build: confirms the changelog, resolves signing credentials from 1Password, runs the release script in tmux, and updates the Sparkle appcast and Homebrew tap.

  • Works in 6 steps: Work from the app repo unless asked… → Check repo state, current version,… → Confirm CHANGELOG.md is complete,… → …
  • Cutting a new signed and notarized CodexBar release
  • SKILL.md covers Start, Key Material, CodexBar and Verify, plus 1 more section
  • Calls python3, brew and gh; reaches andymatuschak.org; needs APP_STORE_CONNECT_KEY_ID

What it does

Work happens from the CodexBar app repo by default, starting with checking the current version, the latest tag or release, and that CHANGELOG.md is complete, deduplicated, user-facing and dated for the release; the repo's own release script is preferred over bypassing it, with small script or test blockers patched rather than worked around. Key material is never printed: App Store Connect credentials (a private key, key id and issuer id) and the Sparkle private key are resolved as 1Password references through a release-private locator file, kept together from the same 1Password item rather than mixed with stale environment values.

A safe-env-file pattern writes only 1Password references, never raw secrets, to a temporary file, which is consumed with op run and then deleted. The normal release runs the repo's release script inside a persistent tmux session so it survives a dropped connection. Named paths cover the release, signing and appcast scripts, the release zip and dSYM assets, the version file, and the separate Homebrew tap repository holding the cask and formula definitions.

When your agent uses it

  • Cutting a new signed and notarized CodexBar release
  • Updating the Sparkle appcast and Homebrew cask after a release
  • Resolving release signing credentials safely from 1Password

Example prompts

  • “Release the next version of CodexBar and update the Homebrew tap.”
  • “Check that CHANGELOG.md is ready, then run the release script.”
  • “Resolve the App Store Connect credentials from 1Password for this release.”

Requirements

  • The op (1Password) CLI
  • tmux
  • The CodexBar repo's release, signing and appcast scripts

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Work from the app repo unless asked otherwise.
  2. Check repo state, current version, latest tag/release, and release docs/scripts.
  3. Confirm CHANGELOG.md is complete, user-facing, deduped, and dated for the release.
  4. Prefer the repo release script; patch small script/test blockers instead of bypassing the release path.
  5. Never print key material. Keep 1Password references and local key paths as references only.
  6. Load $release-private if it exists before resolving Peter-owned credential locators.

What it can do on your machine

Read from SKILL.md and the folder at commit dd7dca4. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python3
    • brew
    • gh
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • andymatuschak.org

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • APP_STORE_CONNECT_KEY_ID

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

CodexBar macOS Release loads about 1.5k tokens when it runs. Until then it costs about 25 tokens; SKILL.md has 442 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~25
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from steipete/CodexBar at commit dd7dca4, republished under its MIT licence (© steipete). 442 words, ~1,468 tokens.

Download SKILL.mdSave it as .claude/skills/release-codexbar/SKILL.md (or your agent's skills folder).
name
release-codexbar
description
CodexBar release: versioning, notarization, appcast, Homebrew, post-release bump.

CodexBar Release

Use for releasing signed/notarized macOS apps, especially repos with Sparkle appcasts and Homebrew casks.

Start

  1. Work from the app repo unless asked otherwise.
  2. Check repo state, current version, latest tag/release, and release docs/scripts.
  3. Confirm CHANGELOG.md is complete, user-facing, deduped, and dated for the release.
  4. Prefer the repo release script; patch small script/test blockers instead of bypassing the release path.
  5. Never print key material. Keep 1Password references and local key paths as references only.
  6. Load $release-private if it exists before resolving Peter-owned credential locators.

Key Material

Use $one-password for secret handling. op only in tmux/persistent shell; no broad env, set, export -p, or secret scans.

Known App Store Connect shape:

  • fields: private_key_p8, key_id, issuer_id
  • keep all three fields from the same 1Password item; do not mix with stale values from ~/.profile
  • resolve Peter-owned item refs from $release-private

Known Sparkle key:

  • resolve the private key file from $release-private
  • pass as SPARKLE_PRIVATE_KEY_FILE

Safe env file pattern:

text
APP_STORE_CONNECT_API_KEY_P8=<1Password ref from release-private>
APP_STORE_CONNECT_KEY_ID=<1Password ref from release-private>
APP_STORE_CONNECT_ISSUER_ID=<1Password ref from release-private>
SPARKLE_PRIVATE_KEY_FILE=<path from release-private>

Run with op run --account my.1password.com --env-file <file> -- <script>, then delete the temp env file.

CodexBar

Paths:

  • repo: ~/Projects/codexbar
  • release script: Scripts/release.sh
  • signing/notarization: Scripts/sign-and-notarize.sh
  • appcast: Scripts/make_appcast.sh, appcast.xml
  • release assets: CodexBar-macos-universal-<version>.zip, CodexBar-macos-universal-<version>.dSYM.zip
  • packaged app: CodexBar.app
  • version file: version.env
  • changelog: CHANGELOG.md
  • Homebrew tap: ~/Projects/homebrew-tap
  • cask: ~/Projects/homebrew-tap/Casks/codexbar.rb
  • formula: ~/Projects/homebrew-tap/Formula/codexbar.rb
  • CLI release workflow: .github/workflows/release-cli.yml

Normal release:

bash
tmux new-session -d -s codexbar-release 'op run --account my.1password.com --env-file /tmp/codexbar-release-op.env -- Scripts/release.sh'
tmux attach -t codexbar-release

If notarization fails with 401 Unauthenticated, rerun using all three App Store Connect fields from the 1Password item above. Mismatched key_id / issuer_id from ~/.profile can cause this.

If widget metadata generation times out, CODEXBAR_WIDGET_METADATA_TIMEOUT_SECONDS=600 is a known-good floor.

CodexBar CLI tarballs are not produced by Scripts/release.sh itself. The GitHub release event triggers .github/workflows/release-cli.yml, which builds and uploads:

  • CodexBarCLI-v<version>-macos-arm64.tar.gz
  • CodexBarCLI-v<version>-macos-x86_64.tar.gz
  • CodexBarCLI-v<version>-linux-aarch64.tar.gz
  • CodexBarCLI-v<version>-linux-x86_64.tar.gz
  • matching .sha256 files

If the workflow fails only in update-homebrew-tap with GitHub API rate limiting, the CLI assets may already be uploaded. Verify assets live, then update Formula/codexbar.rb manually from the tarball checksums.

Show full SKILL.md (135 more words)Show less

Verify

Release is not done until the published chain checks out:

bash
gh release view v<VERSION> --json tagName,name,isDraft,isPrerelease,url,assets,body
Scripts/check-release-assets.sh v<VERSION>
python3 - <<'PY'
import xml.etree.ElementTree as ET
ns={'sparkle':'http://www.andymatuschak.org/xml-namespaces/sparkle'}
root=ET.parse('appcast.xml').getroot()
item=root.find('channel').find('item')
enc=item.find('enclosure')
print(item.findtext('title'))
print(item.findtext('sparkle:version', namespaces=ns))
print(item.findtext('sparkle:shortVersionString', namespaces=ns))
print(enc.attrib.get('url'))
print(enc.attrib.get('length'))
print(bool(enc.attrib.get('{http://www.andymatuschak.org/xml-namespaces/sparkle}edSignature')))
PY
codesign --verify --deep --strict --verbose=2 CodexBar.app
spctl --assess --type execute --verbose CodexBar.app

For Homebrew:

bash
shasum -a 256 CodexBar-macos-universal-<VERSION>.zip
cd /Users/steipete/Projects/homebrew-tap
python3 .github/scripts/update_formula.py --formula codexbar --tag v<VERSION> --repository steipete/CodexBar --artifact-template 'CodexBarCLI-{tag}-{target}.tar.gz' --target-aliases 'darwin_arm64=macos-arm64,darwin_amd64=macos-x86_64,linux_arm64=linux-aarch64,linux_amd64=linux-x86_64'
brew fetch --cask --force --retry codexbar
brew fetch --formula --force --retry steipete/tap/codexbar

Update the cask when app zip assets exist. Update the formula only when standalone CLI tarballs for that version exist.

Tap audit can be noisy from unrelated formulae; keep evidence specific to the app cask.

Closeout

  1. Create/push tag and GitHub release through the release script.
  2. Verify appcast points to the new GitHub release asset with signature and length.
  3. Update/push the Homebrew cask if the app zip changed.
  4. Bump the app repo to next patch Unreleased:
    • version.env: next MARKETING_VERSION, next BUILD_NUMBER
    • CHANGELOG.md: top ## <next> — Unreleased
  5. Commit, push, then pull --ff-only.
  6. Restart the local app from the packaged bundle and verify the running bundle version.
  7. Check no release/notary/op temp sessions or temp env files remain.

CodexBar restart:

bash
pkill -x CodexBar || pkill -f CodexBar.app || true
cd "$(git rev-parse --show-toplevel)"
open -n CodexBar.app
/usr/libexec/PlistBuddy -c 'Print :CFBundleShortVersionString' CodexBar.app/Contents/Info.plist
/usr/libexec/PlistBuddy -c 'Print :CFBundleVersion' CodexBar.app/Contents/Info.plist

© steipete, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/release-codexbar of steipete/CodexBar.

Open the folder on GitHubat commit dd7dca4

Compare with similar skills

CodexBar macOS Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

CodexBar macOS Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
CodexBar macOS Release this skillsteipete/CodexBar22k—~1.5kAutomated safety check: PassMIT
Reproduce macOS Python FlavorsNuitka/Nuitka15k—~1.7kAutomated safety check: PassAGPL-3.0
Daytona Sandbox Operationsdifferent-ai/openwork24k—~917Automated safety check: PassCustom licence
Chezmoi Reconcilenarze/dotfiles174—~1kAutomated safety check: WarnMIT
Upgradenarze/dotfiles174—~795Automated safety check: PassMIT
New Mac Setupswyxio/skills172—~4.3kAutomated safety check: PassMIT

Similar skills

  • Reproduce macOS Nuitka issues across Python distributions and GitHub Actions Python packaging.

    15k GitHub stars~1.7k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Daytona Sandbox Operations

    different-ai/openwork

    Covers Daytona CLI setup, sandbox debugging, keeping a sandbox alive and which credentials the CLI uses, for when Daytona itself is the problem rather than the tests.

    24k GitHub stars~917 tokensUpdated today
    DevOps & CloudAuto-check passed
  • Chezmoi Reconcile

    narze/dotfiles

    Reconcile drift between the local machine and the chezmoi dotfiles repo, deciding per file whether the machine edit or the repo source wins.

    174 GitHub stars~1k tokensUpdated today
    DevOps & CloudAuto-check: warnings
  • Upgrade

    narze/dotfiles

    Update this machine's Collie installation and verify the running bridge.

    174 GitHub stars~795 tokensUpdated today
    DevOps & CloudAuto-check passed
  • New Mac Setup

    swyxio/skills

    Fully automated new Mac setup for fullstack web developers and AI engineers.

    172 GitHub stars~4.3k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed
  • Mac App Release

    steipete/agent-scripts

    Release workflow for Sparkle-updated macOS apps, driven by a repo-owned manifest and a shared script covering appcast, signing, GitHub Release and Homebrew closeout.

    7.3k GitHub stars~2.3k tokensUpdated 2 days ago
    DevOps & CloudAuto-check passed

More from steipete/CodexBar

  • CodexBar Live QA

    steipete/CodexBar

    Runs live QA for the CodexBar app: provider usage matrix checks through its packaged CLI, config validation and menu checks, with 1Password-backed credentials handled safely.

    22k GitHub stars~1.2k tokensUpdated today
    Auto-check passed
  • CodexBar Usage Reader

    steipete/CodexBar

    CodexBar read. Provider usage, limits, credits, config health. JSON. No writes.

    22k GitHub stars~320 tokensUpdated today
    Auto-check passed

Works with

Questions about CodexBar macOS Release

What does CodexBar macOS Release do?

Releases a signed, notarized CodexBar build: confirms the changelog, resolves signing credentials from 1Password, runs the release script in tmux, and updates the Sparkle appcast and Homebrew tap. md is complete, deduplicated, user-facing and dated for the release; the repo's own release script is preferred over bypassing it, with small script or test blockers patched rather than worked around. Key material is never printed: App Store Connect credentials (a private key, key id and issuer id) and the Sparkle private key are resolved as 1Password references through a release-private locator file, kept together from the same 1Password item rather than mixed with stale environment values.

When should I use CodexBar macOS Release?

CodexBar macOS Release fits situations like: cutting a new signed and notarized CodexBar release; updating the Sparkle appcast and Homebrew cask after a release; resolving release signing credentials safely from 1Password.

How do I install CodexBar macOS Release in Claude Code?

Run `npx skills add steipete/CodexBar --skill release-codexbar -a claude-code`. Or copy the skill folder (.agents/skills/release-codexbar in steipete/CodexBar) into .claude/skills/release-codexbar in your project. Claude Code loads it when a task matches its description.

How do I install CodexBar macOS Release in Codex?

Run `npx skills add steipete/CodexBar --skill release-codexbar -a codex`. Or copy the skill folder (.agents/skills/release-codexbar in steipete/CodexBar) into .agents/skills/release-codexbar in your project. Codex loads it when a task matches its description.

Can I use CodexBar macOS Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add steipete/CodexBar --skill release-codexbar -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release-codexbar, .gemini/skills/release-codexbar, .github/skills/release-codexbar and .opencode/skills/release-codexbar in your project.

What does CodexBar macOS Release need to run?

Going by SKILL.md and its folder, CodexBar macOS Release needs the command-line tools its instructions call (python3, brew, gh and git) and credentials named APP_STORE_CONNECT_KEY_ID. Our summary lists: The op (1Password) CLI; tmux; The CodexBar repo's release, signing and appcast scripts.

Does CodexBar macOS Release access the network?

SKILL.md names 1 domain. In commands or code: andymatuschak.org; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is CodexBar macOS Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does CodexBar macOS Release use?

CodexBar macOS Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does CodexBar macOS Release use?

About 1.5k tokens (SKILL.md is roughly 5.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to CodexBar macOS Release?

Skills that share tags, products or a category with CodexBar macOS Release: Reproduce macOS Python Flavors (Nuitka/Nuitka, 15k stars), Daytona Sandbox Operations (different-ai/openwork, 24k stars), Chezmoi Reconcile (narze/dotfiles, 174 stars) and Upgrade (narze/dotfiles, 174 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains CodexBar macOS Release?

steipete (a GitHub user) maintains it in steipete/CodexBar, which has 22,250 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

Source: steipete/CodexBar on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.