Menu
Cut and publish a Blurt release (build, sign, notarize, staple, DMG, GitHub). Use when the user asks to ship/release a new version. User-invoked only — it has real side effects (notarization, git tags, GitHub release).
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Basé sur la classification professionnelle SOC
Blurt's hard "don't do this" rules — architecture decisions that were made deliberately and reverted before. Load this before adding or changing engine/app/build/test code so you don't reintroduce something that was intentionally removed.
Verify the repo is green by running scripts/check.sh — the same full health check CI runs (swift test + coverage gate, sanitizers, xcodegen drift, app build, swift-format/swiftlint/periphery/prettier/markdownlint/shellcheck). Use before claiming a change builds, passes, or is ready to commit/PR. Bakes in the macOS-only guard so a Linux/web sandbox flags "verify on a Mac" instead of fabricating a green result; there, scripts/check.sh --portable runs the platform-independent subset (docs/site/scripts/workflows).
Print a daily Blurt launch KPI snapshot — Blurt.dmg download count, GitHub stars, and repo traffic/referrers — and compare against the campaign's baseline/good/great bands. Use during launch week, or wrap with /loop for a recurring check.
| name | release |
| description | Cut and publish a Blurt release (build, sign, notarize, staple, DMG, GitHub). Use when the user asks to ship/release a new version. User-invoked only — it has real side effects (notarization, git tags, GitHub release). |
| disable-model-invocation | true |
The release pipeline lives in scripts/. Run it from the repo root. Confirm
the target version with the user before publishing — publishing is hard to undo.
main (releases ship from main).blurt-notary is stored in the dedicated signing keychain
(xcrun notarytool store-credentials blurt-notary --keychain ~/Library/Keychains/blurt-signing.keychain-db …).
The build pins every notary call to that keychain, so a profile stored only in
login (or an incidental keychain like electron-builder's) will not be found.scripts/release-bump.sh updates the marketing version
and build number in App/Blurt/project.yml, regenerates the project, and
opens a PR (versions land on main via PR — main is branch-protected).scripts/release-build.sh does the whole Apple
path: xcodebuild Release → sign nested code including any embedded
frameworks (each must get --options runtime --timestamp, or notarization
rejects it) → notarize → staple → DMG → verify.scripts/release-publish.sh creates the GitHub release and
uploads Blurt.dmg (the README's download link points at
releases/latest/download/Blurt.dmg).scripts/release.sh orchestrates the above end-to-end; prefer it unless
debugging a single stage.scripts/check.sh green before releasing — same gate as CI.xcrun stapler validate)./Applications (TCC needs a stable path);
don't redirect it to DerivedData//tmp.Read the script you're about to run before running it, surface what it will do, and get a go-ahead for the publish step.