agentleFS
ignatovvignatovv/VibePad/.claude/skills/release/SKILL.md

release

Skill67 starsChanged 9 months agoMITView on GitHub

Build, notarize, sign, and publish a release of VibePad

  • Deletes or force-pushes
  • Commits and pushes

193 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use create-agent-adapter, changelog-style and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • MicrosoftSkill

    create-agent-adapter

    Technical guide for creating a new Paperclip agent adapter. Use when building a new adapter package, adding support for a new AI coding tool (e.g. a new CLI agent, API-based agent, or custom process), or when modifying the adapter system. Covers the required interfaces, module structure, registration points, and conventions derived from the existing claude-local and codex-local adapters.

    Also in 5 projects that use this

  • GrinvSkill

    changelog-style

    Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR or cutting a release, to write/fix the [Unreleased] section's entries — moving [Unreleased] under a new dated version heading is a separate, automated step (see the release skill / scripts/sync-version.ts), not this skill's job.

    Also in 4 projects that use this

  • GrinvSkill

    docs-consistency-check

    Check README/manifest.json/server.json/CHANGELOG.md/AGENTS.md and docs/*.md for drift against the actual registered tools and source. Use after adding, renaming, or removing a tool, or as part of a live-audit pass.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    component-release

    Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.

    Also in 4 projects that use this

  • Microsoft AzureSkill

    documentation-consistency

    Keeps AI Landing Zone contributor, user, and operator documentation aligned with shipped Bicep behavior. Use for parameters, defaults, outputs, topology, deployment flow, operations, or releases.

    Also in 8 projects that use this

  • rivet-devSkill

    launch-graphics

    Generate agentOS marketing/launch graphics (launch & social heroes, code-snippet cards) from the committed generators in docs-internal/graphics. Use when asked to make, update, or render an agentOS launch image, social image, "agentOS Apps" graphic, or technical code-snippet image.

    Also in 3 projects that use this

  • +3 more from Grinv

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use AskUserQuestion to ask: "Before we start, please make sure your terminal has these permissions enabled in System Settings → Privacy & …

    line 19
  2. Very specific:

    Verify signing: before notarizing — check deep signing, no get-task-allow, and Sparkle helpers:

    line 53
  3. Distinctive:

    If any check fails, stop and report to the user.

    line 59
  4. Very specific:

    If notarization fails, stop and report the error to the user.

    line 88
  5. Distinctive:

    Security reminder: Ask the user to revoke the temporary permissions they granted in step 1: go to System Settings → Privacy & Security and …

    line 110

“Common” is measured: kept by at least 6 in 10 of the 183 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Build a release-ready VibePad: notarize with Apple, sign with Sparkle EdDSA, create a GitHub Release. Optionally bump the version first.

Arguments

The user may pass a version string (e.g. /release 1.1) to bump MARKETING_VERSION before building. If no version is given, use the current version from the project.

Steps

  1. Check terminal permissions — DMG creation requires your terminal to have two macOS permissions. Ask the user to confirm they've granted both before proceeding:

    • Automation → Finder: System Settings → Privacy & Security → Automation → [your terminal app] → enable Finder
    • Full Disk Access: System Settings → Privacy & Security → Full Disk Access → enable [your terminal app]

    Use AskUserQuestion to ask: "Before we start, please make sure your terminal has these permissions enabled in System Settings → Privacy & Security: (1) Automation → Finder, (2) Full Disk Access. Are both enabled?" — do NOT proceed until the user confirms.

  2. If a version argument was provided, update MARKETING_VERSION in the VibePad target's Debug and Release build configurations in VibePad.xcodeproj/project.pbxproj. Also bump CURRENT_PROJECT_VERSION by 1 from its current value. Use the Edit tool — only change the two VibePad target configs (IDs 3DCDC9722F36A1750063EE37 and 3DCDC9732F36A1750063EE37), not the test targets.
  3. Delete stale config so testers get the first-launch onboarding experience:
rm -f ~/.vibepad/config.json
  1. Archive and export (Developer ID signing, timestamps, deep-signs embedded frameworks):
# Archive
xcodebuild archive -scheme VibePad -destination 'platform=macOS' \
  -archivePath /tmp/VibePad.xcarchive 2>&1 | tail -5

# Export with Developer ID signing
xcodebuild -exportArchive \
  -archivePath /tmp/VibePad.xcarchive \
  -exportOptionsPlist ExportOptions.plist \
  -exportPath /tmp/VibePad-export 2>&1 | tail -5
  1. Set the app path from the export:
APP_PATH="/tmp/VibePad-export/VibePad.app"
  1. Read the version from the built app for naming:
VERSION=$(/usr/libexec/PlistBuddy -c "Print CFBundleShortVersionString" "$APP_PATH/Contents/Info.plist")
BUILD=$(/usr/libexec/PlistBuddy -c "Print CFBundleVersion" "$APP_PATH/Contents/Info.plist")
echo "Version: $VERSION ($BUILD)"
  1. Verify signing before notarizing — check deep signing, no get-task-allow, and Sparkle helpers:
codesign --verify --deep --strict "$APP_PATH"
codesign -d --entitlements - "$APP_PATH" 2>&1  # must NOT contain get-task-allow
codesign -dvv "$APP_PATH/Contents/Frameworks/Sparkle.framework/Versions/B/Autoupdate" 2>&1 | grep Authority

If any check fails, stop and report to the user.

  1. Create pretty DMG with branded background and Applications drop link (NOT zip — Finder's Archive Utility corrupts code signatures when extracting zips):
STAGING="/tmp/VibePad-dmg-staging"
rm -rf "$STAGING" && mkdir -p "$STAGING"
cp -R "$APP_PATH" "$STAGING/"
chflags -R nouchg "$STAGING/"          # unlock files (Sonoma+ uchg bug)

create-dmg \
  --volname "VibePad" \
  --volicon "$APP_PATH/Contents/Resources/AppIcon.icns" \
  --background "/Users/vyuignatiov/code/VibePad/dmg-resources/background@2x.png" \
  --window-pos 200 120 \
  --window-size 660 400 \
  --icon-size 128 \
  --text-size 14 \
  --icon "VibePad.app" 180 220 \
  --hide-extension "VibePad.app" \
  --app-drop-link 480 220 \
  "/Users/vyuignatiov/code/VibePad/VibePad-${VERSION}.dmg" \
  "$STAGING/"
  1. Notarize the DMG (DMGs can be submitted directly — no zip wrapper needed):
xcrun notarytool submit "/Users/vyuignatiov/code/VibePad/VibePad-${VERSION}.dmg" --keychain-profile "vibepad" --wait
xcrun stapler staple "/Users/vyuignatiov/code/VibePad/VibePad-${VERSION}.dmg"

If notarization fails, stop and report the error to the user. Use xcrun notarytool log <submission-id> --keychain-profile "vibepad" to get the detailed error log.

  1. Sign with Sparkle's EdDSA key:
SPARKLE_BIN=$(ls -td /Users/vyuignatiov/Library/Developer/Xcode/DerivedData/VibePad-*/SourcePackages/artifacts/sparkle/Sparkle/bin 2>/dev/null | head -1)
"$SPARKLE_BIN/sign_update" "/Users/vyuignatiov/code/VibePad/VibePad-${VERSION}.dmg"

This prints sparkle:edSignature="..." and length="..." — save these values.

  1. Create git tag and GitHub Release:
git tag v${VERSION}
git push origin v${VERSION}
gh release create v${VERSION} "/Users/vyuignatiov/code/VibePad/VibePad-${VERSION}.dmg" --title "VibePad ${VERSION}" --generate-notes
  1. Report to the user and revoke permissions:
  • Path to the signed DMG
  • The version and build number
  • The sparkle:edSignature and length values (they'll need these for the appcast)
  • The GitHub Release URL
  • Remind them to run /update-site next to update the website and auto-update feed
  • Security reminder: Ask the user to revoke the temporary permissions they granted in step 1: go to System Settings → Privacy & Security and disable Automation → Finder and Full Disk Access for their terminal app. These are only needed during the release process and should not stay enabled.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.