release-mac-app
macOS app release: Sparkle, notarization, GitHub Release, Homebrew, closeout.
What this skill does
# Mac App Release Use for BlackBar, RepoBar, CodexBar, Trimmy, and similar Sparkle-updated macOS apps. ## Rules - Work from the app repo. - Read `.mac-release.env`; it is the repo-owned release manifest. - Use `scripts/mac-release` from this skill for shared release/appcast/verify work. - Keep app-specific build/package/sign behavior in repo scripts unless it is already manifest-driven. - Never print private key material. - Prefer Keychain Sparkle signing. `SPARKLE_PRIVATE_KEY_FILE` is an explicit override only. ## Commands ```bash /Users/steipete/Projects/agent-scripts/skills/release-mac-app/scripts/mac-release status /Users/steipete/Projects/agent-scripts/skills/release-mac-app/scripts/mac-release notes [version] [output.md] /Users/steipete/Projects/agent-scripts/skills/release-mac-app/scripts/mac-release changelog-html <version> [CHANGELOG.md] /Users/steipete/Projects/agent-scripts/skills/release-mac-app/scripts/mac-release make-appcast <zip> [feed-url] /Users/steipete/Projects/agent-scripts/skills/release-mac-app/scripts/mac-release verify-appcast [version] /Users/steipete/Projects/agent-scripts/skills/release-mac-app/scripts/mac-release check-assets [tag] /Users/steipete/Projects/agent-scripts/skills/release-mac-app/scripts/mac-release release ``` ## Manifest Each repo owns `.mac-release.env`. It must contain no secrets. Required: - `MAC_RELEASE_APP_NAME` - `MAC_RELEASE_REPO` - `MAC_RELEASE_BUNDLE_ID` - `MAC_RELEASE_VERSION_FILE` - `MAC_RELEASE_APPCAST` - `MAC_RELEASE_FEED_URL` - `MAC_RELEASE_DOWNLOAD_URL_PREFIX` - `MAC_RELEASE_APP_ZIP` - either `MAC_RELEASE_INFO_PLIST` or `MAC_RELEASE_SUPUBLIC_ED_KEY` - `MAC_RELEASE_PACKAGE_CMD` Common optional: - `MAC_RELEASE_PRECHECK` - `MAC_RELEASE_SOURCE_FILES` (space-separated app helper files to source before expanding artifact names) - `MAC_RELEASE_DSYM_ZIP` - `MAC_RELEASE_REQUIRE_DSYM=0` for app-only releases - `MAC_RELEASE_ARTIFACT_PREFIX` - `MAC_RELEASE_TAG_SIGNED` - `MAC_RELEASE_TAG_FORCE` - `MAC_RELEASE_RELEASE_BRANCH` - `MAC_RELEASE_SPARKLE_ACCOUNT` - `MAC_RELEASE_SPARKLE_CHANNEL` - `MAC_RELEASE_GENERATE_APPCAST_ARGS` - `MAC_RELEASE_RUN_SPARKLE_UPDATE_TEST` - `MAC_RELEASE_SIGNING_KEY_FILE` (local fallback path only; Keychain is used when the file is absent) - `MAC_RELEASE_EXTRA_ASSET_PATTERNS` - `MAC_RELEASE_EXTRA_ASSET_WAIT_SECONDS` - `MAC_RELEASE_EXTRA_ASSET_WAIT_INTERVAL` - `MAC_RELEASE_OP_ITEM` + `MAC_RELEASE_OP_FIELDS` for required packaging secrets. The release helper reads the known item once via `op` inside one persistent tmux session, then exports the requested fields for the package command. - `MAC_RELEASE_OP_ACCOUNT` defaults to `my.1password.com`; `MAC_RELEASE_OP_VAULT`, `MAC_RELEASE_OP_TMUX_SESSION`, `MAC_RELEASE_OP_WAIT_SECONDS` are optional. Without a vault, service-account token env is unset for that single `op` read so the personal desktop account handles it. - `MAC_RELEASE_RUN_LOGIN_SHELL=1` opts command hooks back into `bash -lc`; default hooks use `env -u BASH_ENV bash -c` so shell startup files cannot override exported release secrets. 1Password rules: - Prefer already-exported env vars first; no `op` call if all `MAC_RELEASE_OP_FIELDS` are present. - If fields are missing, use exactly one `op item get` inside tmux for the whole release. - Use service-account mode only with an explicit vault or `MAC_RELEASE_OP_USE_SERVICE_ACCOUNT=1`. - Do not retry `op` reads in a fresh shell; rerun only from the same tmux session after explicit user direction. ## Done - appcast entry has URL, length, Sparkle signature. - downloaded enclosure verifies with Sparkle. - extracted app passes `codesign`, `spctl`, and `stapler validate`. - GitHub release has app zip, dSYM zip when configured, plus app-specific extra assets. - release notes match the changelog section. - after verified release, bump changelog to next patch `Unreleased` in the app repo.
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.