بنقرة واحدة
release-slug
Ship a signed, notarized, auto-updating release of __APP_DISPLAY__. Use when cutting a new version.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Ship a signed, notarized, auto-updating release of __APP_DISPLAY__. Use when cutting a new version.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | release-__SLUG__ |
| description | Ship a signed, notarized, auto-updating release of __APP_DISPLAY__. Use when cutting a new version. |
One command does the whole pipeline: macos release __SLUG__. This skill is the checklist around it.
## Unreleased into a dated ## X.Y.Z - YYYY-MM-DD
section. Entries are user-facing prose — what someone notices, not internal churn. This text
becomes the GitHub release notes and the Sparkle appcast description verbatim.macos bump __SLUG__ --version X.Y.Z (or macos bump __SLUG__ to bump just
the build number). The build number must strictly increase — Sparkle compares on it.macos release __SLUG__ --dry-run — it lists every step and flags anything missing.macos release __SLUG__
It runs: preflight → swift test → build+sign+notarize+staple → GitHub release (zip + dSYM) →
EdDSA-signed appcast (committed + pushed) → Homebrew cask → bump build number. It's idempotent and
fail-fast; re-running after a fix is safe.
appcast.xml has the new <item> with an sparkle:edSignature.curl -I <url>).brew install --cask __SLUG__ (if a tap is configured) installs the new version.A release isn't done until that chain checks out.
~/.config/macos — never hardcode or commit them.Read-only inspection of __APP_DISPLAY__ — config, version, and current status. Never mutates config, credentials, or releases.
Build, launch, and verify __APP_DISPLAY__ in the menu bar after a change. Confirms the running build is the one you just built.
Use the macOS app blueprint to shape new native menu bar apps under ~/apps/macos. Use when deciding a menu bar app's data source, whether it needs the credentials/networking/oauth/icon-render modules, its distribution path (Developer ID direct vs Mac App Store), how the menu and settings are structured, or whether an idea needs native work beyond the menu bar (sidebar/full window). Pairs with the `macos` CLI skill for commands.
Use the local `macos` CLI to scaffold, run, sign, notarize, and release native macOS menu bar apps. Triggers on creating a new menu bar app, running/building/signing a macOS app, setting up Developer ID signing or notarization, cutting a release with Sparkle auto-update, generating a Homebrew cask, or managing the macOS app inventory under ~/apps/macos.