What problem does it solve? Cutting a Rapture for Mac release involves a fragile sequence of steps — building, signing, notarizing, stapling, DMG packaging, Sparkle appcast signing, changelog cutting, and GitHub Release publishing — where small mistakes (tagging the wrong commit, missing Sparkle keys, unpushed tags) silently break auto-updates or produce mismatched versions. ## Core Features & Use Cases - End-to-end release pipeline: Runs Scripts/release.sh to build, Developer ID sign, notarize twice (app and DMG), staple, and package the DMG, then verifies notarization status and Sparkle appcast updates. - Version and tag discipline: Enforces the rule that version equals git commit count and the release tag must point at the build commit, not the changelog-cut commit, avoiding off-by-one version tags. - Publish ritual: Cuts the CHANGELOG, updates the roadmap status, commits and pushes main, pushes the tag, and creates the GitHub Release with the DMG attached. - Use Case: A maintainer says "cut a release" and the skill walks through preflight checks (keychain profile, sign_update on PATH, EdDSA key match), runs the pipeline, and publishes v1.0.NN with correct notes and SHA-256. ## Quick Start Ask the assistant to cut a new Rapture for Mac release and publish it to GitHub Releases.
