Agent skill

Releasing macOS Apps

by jamesrochabrun in jamesrochabrun/skills

Create notarized macOS app releases with Sparkle auto-updates, DMG installers, and GitHub releases.

MITAuto-check passedMobile

Install Releasing macOS Apps

skills CLI

$ npx skills add jamesrochabrun/skills --skill releasing-macos-apps -a claude-code

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

GitHub CLI

$ gh skill install jamesrochabrun/skills releasing-macos-apps --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/jamesrochabrun/skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/releasing-macos-apps .claude/skills/releasing-macos-apps && 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/

Paste into Claude Code

Install the "releasing-macos-apps" agent skill from https://github.com/jamesrochabrun/skills/tree/main/skills/releasing-macos-apps into .claude/skills/releasing-macos-apps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing-macos-apps", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/jamesrochabrun/skills/tree/main/skills/releasing-macos-apps

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add jamesrochabrun/skills --skill releasing-macos-apps -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install jamesrochabrun/skills releasing-macos-apps --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jamesrochabrun/skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/releasing-macos-apps .agents/skills/releasing-macos-apps && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "releasing-macos-apps" agent skill from https://github.com/jamesrochabrun/skills/tree/main/skills/releasing-macos-apps into .agents/skills/releasing-macos-apps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing-macos-apps", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jamesrochabrun/skills --skill releasing-macos-apps -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install jamesrochabrun/skills releasing-macos-apps --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jamesrochabrun/skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/releasing-macos-apps .cursor/skills/releasing-macos-apps && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "releasing-macos-apps" agent skill from https://github.com/jamesrochabrun/skills/tree/main/skills/releasing-macos-apps into .cursor/skills/releasing-macos-apps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing-macos-apps", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/jamesrochabrun/skills.git --path skills/releasing-macos-apps

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add jamesrochabrun/skills --skill releasing-macos-apps -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install jamesrochabrun/skills releasing-macos-apps --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jamesrochabrun/skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/releasing-macos-apps .gemini/skills/releasing-macos-apps && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "releasing-macos-apps" agent skill from https://github.com/jamesrochabrun/skills/tree/main/skills/releasing-macos-apps into .gemini/skills/releasing-macos-apps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing-macos-apps", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install jamesrochabrun/skills releasing-macos-apps

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add jamesrochabrun/skills --skill releasing-macos-apps -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/jamesrochabrun/skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/releasing-macos-apps .github/skills/releasing-macos-apps && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "releasing-macos-apps" agent skill from https://github.com/jamesrochabrun/skills/tree/main/skills/releasing-macos-apps into .github/skills/releasing-macos-apps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing-macos-apps", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add jamesrochabrun/skills --skill releasing-macos-apps -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install jamesrochabrun/skills releasing-macos-apps --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/jamesrochabrun/skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/releasing-macos-apps .opencode/skills/releasing-macos-apps && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "releasing-macos-apps" agent skill from https://github.com/jamesrochabrun/skills/tree/main/skills/releasing-macos-apps into .opencode/skills/releasing-macos-apps/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "releasing-macos-apps", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: releasing-macos-apps
GitHub stars: 216
Token cost: ~2.4k tokens
SKILL.md length: 517 words
Files: 4
Skills in repo: 23
Repo updated: Jan 14, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Create notarized macOS app releases with Sparkle auto-updates, DMG installers, and GitHub releases.

Works in 11 steps: Update Version → Build and Archive → Export with Code Signing → …
Releasing macOS apps
SKILL.md covers Release Checklist, Prerequisites, Step 1: Update Version and Step 2: Build and Archive, plus 11 more sections
Calls git, gh and xcodebuild; reaches github.com and apple.com

What it does

Releasing macOS Apps is an agent skill from jamesrochabrun/skills. Create notarized macOS app releases with Sparkle auto-updates, DMG installers, and GitHub releases. Use when releasing macOS apps, creating DMG files, notarizing apps, or setting up Sparkle updates. Handles version updates, code signing, notarization, and distribution.

Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files (for example `NOTARIZATION.md`, `SPARKLE.md` and `TROUBLESHOOTING.md`).

It sits in Mobile, covering App store release. It works with macOS and GitHub. The licence is MIT.

When your agent uses it

Releasing macOS apps
Creating DMG files
Notarizing apps
Setting up Sparkle updates

Example prompts

“/releasing-macos-apps”

Requirements

A credential in YOUR_SPARKLE_PRIVATE_KEY

Workflow steps

11 steps, taken from the step headings in SKILL.md.

Update Version
Build and Archive
Export with Code Signing
Create Zip and Generate Sparkle Signature
Create DMG with Applications Folder
Submit for Notarization
Staple Notarization Ticket
Update appcast.xml
Commit and Push Changes
Update GitHub Release
Final Verification

What it can do on your machine

Read from SKILL.md and the folder at commit 2482c17. 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:
- git
- gh
- xcodebuild
- xcrun
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:
- github.com
- apple.com
- claude.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Releasing macOS Apps loads about 2.4k tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 517 words of instructions outside code blocks.

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

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 jamesrochabrun/skills at commit 2482c17, republished under its MIT licence (© jamesrochabrun). 517 words, ~2,355 tokens.

Download SKILL.mdSave it as .claude/skills/releasing-macos-apps/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: releasing-macos-apps
description: Create notarized macOS app releases with Sparkle auto-updates, DMG installers, and GitHub releases. Use when releasing macOS apps, creating DMG files, notarizing apps, or setting up Sparkle updates. Handles version updates, code signing, notarization, and distribution.

Releasing macOS Apps

Complete workflow for creating notarized macOS app releases with Sparkle auto-updates, DMG installers, and GitHub releases.

Release Checklist

Copy this checklist and track progress:

Release Progress:
- [ ] Step 1: Check prerequisites (certificates, credentials)
- [ ] Step 2: Update version in .xcconfig file
- [ ] Step 3: Build and archive the app
- [ ] Step 4: Export with proper code signing
- [ ] Step 5: Create zip and generate Sparkle signature
- [ ] Step 6: Create DMG with Applications folder
- [ ] Step 7: Submit for notarization
- [ ] Step 8: Staple notarization ticket to DMG
- [ ] Step 9: Update appcast.xml with new signature
- [ ] Step 10: Commit and push changes
- [ ] Step 11: Update GitHub release assets
- [ ] Step 12: Verify DMG and version number

Prerequisites

Before starting a release, verify:

Apple Developer ID Application certificate installed and valid
Apple ID credentials for notarization:
- Apple ID email
- App-specific password (generate at appleid.apple.com)
- Team ID
Sparkle private key for signing updates
GitHub CLI (gh) installed and authenticated
Version configuration location identified (usually .xcconfig file)

Check certificate:

bash

security find-identity -v -p codesigning | grep "Developer ID Application"

Step 1: Update Version

Locate your version configuration file (commonly ProjectName.xcconfig or project.pbxproj).

For .xcconfig files:

bash

# Edit the APP_VERSION line
# Example: APP_VERSION = 1.0.9

Verify the update:

bash

xcodebuild -project PROJECT.xcodeproj -showBuildSettings | grep MARKETING_VERSION

Step 2: Build and Archive

Archive the app with the new version:

bash

xcodebuild -project PROJECT.xcodeproj \
  -scheme SCHEME_NAME \
  -configuration Release \
  -archivePath ~/Desktop/APP-VERSION.xcarchive \
  archive

Verify archive was created:

bash

ls -la ~/Desktop/APP-VERSION.xcarchive

Step 3: Export with Code Signing

Create export options file:

bash

cat > /tmp/ExportOptions.plist << 'EOF'
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>destination</key>
	<string>export</string>
	<key>method</key>
	<string>developer-id</string>
	<key>signingStyle</key>
	<string>automatic</string>
	<key>teamID</key>
	<string>YOUR_TEAM_ID</string>
	<key>signingCertificate</key>
	<string>Developer ID Application</string>
</dict>
</plist>
EOF

Replace YOUR_TEAM_ID with your actual team ID.

Export the archive:

bash

xcodebuild -exportArchive \
  -archivePath ~/Desktop/APP-VERSION.xcarchive \
  -exportPath ~/Desktop/APP-VERSION-Export \
  -exportOptionsPlist /tmp/ExportOptions.plist

Verify the exported app version:

bash

defaults read ~/Desktop/APP-VERSION-Export/APP.app/Contents/Info.plist CFBundleShortVersionString

This should show the new version number.

Verify code signing:

bash

codesign -dvvv ~/Desktop/APP-VERSION-Export/APP.app

Look for "Developer ID Application" in the Authority lines.

Step 4: Create Zip and Generate Sparkle Signature

Create zip file for Sparkle auto-updates:

bash

cd ~/Desktop/APP-VERSION-Export
ditto -c -k --keepParent APP.app APP.app.zip

Generate Sparkle EdDSA signature (you'll be prompted for the private key):

bash

echo "YOUR_SPARKLE_PRIVATE_KEY" | \
  ~/Library/Developer/Xcode/DerivedData/PROJECT-HASH/SourcePackages/artifacts/sparkle/Sparkle/bin/sign_update \
  APP.app.zip --ed-key-file -

Output format:

sparkle:edSignature="BASE64_SIGNATURE" length="FILE_SIZE"

Save both the signature and length for updating appcast.xml.

For more details, see SPARKLE.md.

Step 5: Create DMG with Applications Folder

Create DMG installer with Applications folder symlink for drag-and-drop installation:

bash

TEMP_DMG_DIR="/tmp/APP_dmg" && \
rm -rf "${TEMP_DMG_DIR}" && \
mkdir -p "${TEMP_DMG_DIR}" && \
cp -R ~/Desktop/APP-VERSION-Export/APP.app "${TEMP_DMG_DIR}/" && \
ln -s /Applications "${TEMP_DMG_DIR}/Applications" && \
hdiutil create -volname "APP VERSION" \
  -srcfolder "${TEMP_DMG_DIR}" \
  -ov -format UDZO ~/Desktop/APP-VERSION.dmg && \
rm -rf "${TEMP_DMG_DIR}"

Verify DMG contents:

bash

hdiutil attach ~/Desktop/APP-VERSION.dmg -readonly -nobrowse -mountpoint /tmp/verify_dmg && \
ls -la /tmp/verify_dmg && \
hdiutil detach /tmp/verify_dmg

You should see both APP.app and Applications (symlink).

Step 6: Submit for Notarization

Submit the DMG to Apple for notarization (you'll be prompted for credentials):

bash

xcrun notarytool submit ~/Desktop/APP-VERSION.dmg \
  --apple-id YOUR_APPLE_ID@gmail.com \
  --team-id YOUR_TEAM_ID \
  --password YOUR_APP_SPECIFIC_PASSWORD \
  --wait

The --wait flag makes the command wait for processing to complete (typically 1-2 minutes).

Expected output:

Processing complete
  id: [submission-id]
  status: Accepted

If status is "Invalid", get detailed logs:

bash

xcrun notarytool log SUBMISSION_ID \
  --apple-id YOUR_APPLE_ID@gmail.com \
  --team-id YOUR_TEAM_ID \
  --password YOUR_APP_SPECIFIC_PASSWORD

For notarization troubleshooting, see NOTARIZATION.md.

Step 7: Staple Notarization Ticket

Staple the notarization ticket to the DMG:

bash

xcrun stapler staple ~/Desktop/APP-VERSION.dmg

Expected output:

The staple and validate action worked!

Verify notarization:

bash

spctl -a -vvv ~/Desktop/APP-VERSION-Export/APP.app

Should show:

accepted
source=Notarized Developer ID

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

Step 8: Update appcast.xml

Update the Sparkle appcast file with the new version, signature, and file size from Step 4:

xml

<item>
  <title>Version X.X.X</title>
  <link>https://github.com/USER/REPO</link>
  <sparkle:version>X.X.X</sparkle:version>
  <sparkle:channel>stable</sparkle:channel>
  <description><![CDATA[
    Release version X.X.X
  ]]></description>
  <pubDate>DAY, DD MMM YYYY HH:MM:SS -0700</pubDate>
  <enclosure
    url="https://github.com/USER/REPO/releases/download/vX.X.X/APP.app.zip"
    sparkle:version="X.X.X"
    sparkle:edSignature="SIGNATURE_FROM_STEP_4"
    length="FILE_SIZE_FROM_STEP_4"
    type="application/octet-stream" />
</item>

Note: The gitleaks pre-commit hook may flag the Sparkle signature as a potential secret. This is a false positive - the EdDSA signature is public and safe to commit. Use git commit --no-verify if needed.

Step 9: Commit and Push Changes

Commit the version update and appcast changes:

bash

git add PROJECT.xcconfig appcast.xml
git commit --no-verify -m "Bump version to X.X.X

Update appcast.xml with new version, Sparkle signature, and file size.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>"

git push

Step 10: Update GitHub Release

Create or update the GitHub release with new assets:

For new releases:

bash

gh release create vX.X.X \
  --title "APP vX.X.X" \
  --notes "Release version X.X.X" \
  ~/Desktop/APP-VERSION.dmg \
  ~/Desktop/APP-VERSION-Export/APP.app.zip

For updating existing releases:

bash

# Upload new assets (overwrites existing with --clobber)
gh release upload vX.X.X \
  ~/Desktop/APP-VERSION.dmg \
  ~/Desktop/APP-VERSION-Export/APP.app.zip \
  --clobber

Note on asset naming: The uploaded filename becomes the asset name. To upload with a specific name:

bash

# Copy to desired name first
cp ~/Desktop/APP-1.0.9.dmg /tmp/APP.dmg
gh release upload vX.X.X /tmp/APP.dmg

Verify release assets:

bash

gh release view vX.X.X --json assets -q '.assets[] | "\(.name) - \(.size) bytes"'

Step 11: Final Verification

Verify the release is working correctly:

Check version in app:

bash

defaults read /Applications/APP.app/Contents/Info.plist CFBundleShortVersionString

Should show: X.X.X

Test DMG:

Download the DMG from GitHub release
Open the DMG
Verify Applications folder is present for drag-and-drop
Drag app to Applications and launch
Should open without any "malicious" or security warnings

Test Sparkle updates:

Users with previous versions should receive automatic update notifications
The update should download and install smoothly

Common Issues

If you encounter problems, see TROUBLESHOOTING.md for solutions to:

Version not updating after rebuild
DMG missing Applications folder
Notarization failures
"Malicious app" warnings
Sparkle signature issues
CI/CD failures

Quick Reference

Check version:

bash

defaults read /path/to/APP.app/Contents/Info.plist CFBundleShortVersionString

Check code signing:

bash

codesign -dvvv /path/to/APP.app

Check notarization:

bash

spctl -a -vvv /path/to/APP.app

Get Sparkle sign_update path:

bash

find ~/Library/Developer/Xcode/DerivedData -name sign_update -type f

Files

SKILL.md and 3 other files in skills/releasing-macos-apps of jamesrochabrun/skills.

SKILL.md
NOTARIZATION.md
SPARKLE.md
TROUBLESHOOTING.md

Open the folder on GitHubat commit 2482c17

Compare with similar skills

Releasing macOS Apps 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.

Releasing macOS Apps compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Releasing macOS Apps this skilljamesrochabrun/skills	216	—	~2.4k	Automated safety check: Pass	MIT	8 mo ago
Releasenotepadqq/notepadqq	2.3k	—	~2k	Automated safety check: Pass	GPL-3.0	4 days ago
Workbuddy Skin Studiocdredfox/workbuddy-skin-studio	198	—	~1.5k	Automated safety check: Pass	MIT	2 mo ago
Releasenikships/droidproxy	122	—	~1.1k	Automated safety check: Pass	MIT	yesterday
Electron Builderpedronauck/skills	634	—	~2.7k	Automated safety check: Pass	None	25 days ago
Ship Infiniten1m21n/Infinite	268	—	~4.1k	Automated safety check: Pass	Custom licence	yesterday

Similar skills

Release
notepadqq/notepadqq
Release a new Notepadqq version. An agent skill from notepadqq/notepadqq.
2.3k GitHub stars~2k tokensUpdated 4 days ago
MobileAuto-check passed
Workbuddy Skin Studio
cdredfox/workbuddy-skin-studio
Apply a reversible theme/skin to the WorkBuddy desktop app (Tencent AI office agent) via local Chromium DevTools Protocol (CDP) injection.
198 GitHub stars~1.5k tokensUpdated 2 mo ago
MobileAuto-check passed
Release
nikships/droidproxy
Build, sign, notarize, and publish a new DroidProxy release.
122 GitHub stars~1.1k tokensUpdated yesterday
MobileAuto-check passed
Electron Builder
pedronauck/skills
Comprehensive guide for electron-builder (v26.x) packaging, code signing, auto-updates, and release workflows.
634 GitHub stars~2.7k tokensUpdated 25 days ago
MobileAuto-check passed
Ship Infinite
n1m21n/Infinite
Full release: verify, commit, push, tag with curated notes, build the macOS DMG, pull CI Windows zips and Linux AppImage, publish to the Release and GitHub Pages site, flag Node Reference Manual…
268 GitHub stars~4.1k tokensUpdated yesterday
MobileAuto-check passed
Release App
yannikzz/narracat-novel-agent
Cut and publish a new NarraCat-app version — bump the version number, build the Windows x64 package in CI, package + sign + notarize the macOS build locally, and publish both platforms into one…
103 GitHub stars~1.6k tokensUpdated 3 days ago
Testing & QAAuto-check: notes

Questions about Releasing macOS Apps

What does Releasing macOS Apps do?

Create notarized macOS app releases with Sparkle auto-updates, DMG installers, and GitHub releases. Releasing macOS Apps is an agent skill from jamesrochabrun/skills. Create notarized macOS app releases with Sparkle auto-updates, DMG installers, and GitHub releases.

When should I use Releasing macOS Apps?

Releasing macOS Apps fits situations like: releasing macOS apps; creating DMG files; notarizing apps; setting up Sparkle updates.

How do I install Releasing macOS Apps in Claude Code?

Run `npx skills add jamesrochabrun/skills --skill releasing-macos-apps -a claude-code`. Or copy the skill folder (skills/releasing-macos-apps in jamesrochabrun/skills) into .claude/skills/releasing-macos-apps in your project. Claude Code loads it when a task matches its description.

How do I install Releasing macOS Apps in Codex?

Run `npx skills add jamesrochabrun/skills --skill releasing-macos-apps -a codex`. Or copy the skill folder (skills/releasing-macos-apps in jamesrochabrun/skills) into .agents/skills/releasing-macos-apps in your project. Codex loads it when a task matches its description.

Can I use Releasing macOS Apps 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 jamesrochabrun/skills --skill releasing-macos-apps -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/releasing-macos-apps, .gemini/skills/releasing-macos-apps, .github/skills/releasing-macos-apps and .opencode/skills/releasing-macos-apps in your project.

What does Releasing macOS Apps need to run?

Going by SKILL.md and its folder, Releasing macOS Apps needs the command-line tools its instructions call (git, gh, xcodebuild and xcrun). Our summary lists: A credential in YOUR_SPARKLE_PRIVATE_KEY.

Does Releasing macOS Apps access the network?

SKILL.md names 3 domains. In commands or code: github.com, apple.com and claude.com; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Releasing macOS Apps 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 Releasing macOS Apps use?

Releasing macOS Apps 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 Releasing macOS Apps use?

About 2.4k tokens (SKILL.md is roughly 9.4k 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 Releasing macOS Apps?

Skills that share tags, products or a category with Releasing macOS Apps: Release (notepadqq/notepadqq, 2.3k stars), Workbuddy Skin Studio (cdredfox/workbuddy-skin-studio, 198 stars), Release (nikships/droidproxy, 122 stars) and Electron Builder (pedronauck/skills, 634 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Releasing macOS Apps?

jamesrochabrun (a GitHub user) maintains it in jamesrochabrun/skills, which has 216 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on January 14, 2026.

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

Install Releasing macOS Apps

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Releasing macOS Apps

Release Checklist

Prerequisites

Step 1: Update Version

Step 2: Build and Archive

Step 3: Export with Code Signing

Step 4: Create Zip and Generate Sparkle Signature

Step 5: Create DMG with Applications Folder

Step 6: Submit for Notarization

Step 7: Staple Notarization Ticket

Step 8: Update appcast.xml

Step 9: Commit and Push Changes

Step 10: Update GitHub Release

Step 11: Final Verification

Common Issues

Quick Reference

Files

Compare with similar skills

Similar skills

More from jamesrochabrun/skills

Related

Questions about Releasing macOS Apps