Automates the end-to-end release pipeline for Scrutinizer Electron apps.
Install
mkdir -p .claude/skills/release-andyed && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/14724" && unzip -o skill.zip -d .claude/skills/release-andyed && rm skill.zipInstalls to .claude/skills/release-andyed
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Build, sign, notarize, and ship a Scrutinizer Electron release with golden captures and website update.Key capabilities
- →Bump application version (patch or minor).
- →Run automated tests for the application.
- →Capture and compare golden screenshots.
- →Build signed DMG and ZIP files.
- →Create GitHub releases with assets and release notes.
- →Update website download links and version badges.
How it works
This skill executes a sequence of commands to prepare, build, sign, and publish a Scrutinizer Electron release, including version bumping, testing, golden screenshot management, and website updates. It also supports silent rebuilds for hotfixes.
Inputs & outputs
When to use release
- →Bump application version
- →Run automated release tests
- →Generate golden screenshots
- →Package and sign DMG files
About this skill
/release: Scrutinizer
This is the only release procedure for Scrutinizer. DEPLOY.md and docs/release-process.md point here. A personal skill with the same name outranks a project skill, so ~/.claude/skills/release/SKILL.md must stay a short pointer to this file and never hold steps of its own. The pointer is also what a session started in ~/Documents/dev sees first, because this repo's .claude/skills/ loads only after a file in the repo has been read.
Run the steps in order and stop on any failure. Each push, tag push, gh release call and site deploy is public. Andy's go-ahead for them must be given in the session doing the release, because an approval relayed from another session is refused.
Usage
/release X.Y.Z # set package.json to X.Y.Z and release it
/release patch # next patch version (2.8.1 → 2.8.2)
/release minor # next minor version (2.8.1 → 2.9.0)
/release # propose the next patch version, confirm it with Andy
/release silent # rebuild and re-upload the current version: no bump, no tag, no notes
Release types
| Type | Version | Release body | Blog | Site |
|---|---|---|---|---|
| Major | x.Y.0 | docs/release_notes_vX.Y.0.md | new post in scrutinizer-www/src/blog/ | homepage links, new post |
| Dot | x.y.Z, Z > 0 | dot-release template (step 8), links the parent post | none | homepage links, parent post's Download section |
| Silent | current | unchanged | none | none (the DMG filename is unchanged) |
Prerequisites
- macOS with the Xcode command-line tools
- the Developer ID Application certificate in the login keychain (setup history:
docs/archive/release-prep.md) .envin the main checkout withAPPLE_ID,APPLE_ID_PASSWORD,APPLE_TEAM_IDghauthenticated with push access toandyed/scrutinizer2025scrutinizer-wwwcloned at~/Documents/dev/scrutinizer-repo/scrutinizer-www
Fixed facts
- Checkout.
.envis gitignored and exists only in the main checkout,~/Documents/dev/scrutinizer-repo/scrutinizer2025.npm run buildpackages the working tree, not a commit. Release from the main checkout when nothing that ships is modified there; otherwise release from a worktree atorigin/mainwith.envlinked in (step 1b). v2.8.2 was released from a worktree. - Branches. The checkout lives on
agent/usability-study-links. Localmainis stale and unused. Don't check it out and don'tgit push origin main. Releases push the tested sha to bothrefs/heads/mainandrefs/heads/agent/usability-study-links(step 7). - Shared tree. Other sessions work in this checkout. Stage by explicit path, never
git add -A, and never stash WIP you didn't write. As of 2026-10-20,docs/specs/browser-features-and-extensions.mdholds another session's uncommitted notes. - Build. arm64 only, one
package.jsonat the root.npm run buildrunsscripts/build-signed.js: electron-builder, Developer ID signing, then notarization throughscripts/notarize.js(theafterSignhook, 5–15 min). - Three assets.
dist/Scrutinizer-X.Y.Z-arm64.dmg,dist/Scrutinizer-X.Y.Z-arm64-mac.zip,dist/latest-mac.yml. electron-updater readsreleases/latest, thenlatest-mac.yml, then the ZIP. The DMG is only the manual download. A release without the yml makes every installed copy's update check fail withCannot find latest-mac.yml ... HttpError: 404. v2.7.1 and v2.7.2 shipped DMG-only and broke the updater that way (repaired 2026-10-19). - Updater feed. The
publishconfig inpackage.jsonisprovider: github,owner: andyed,repo: scrutinizer2025. - Golden captures go to
tests/golden-captures/vX.Y/, the minor-version folder, so dot releases write into their major's folder. - Website.
~/Documents/dev/scrutinizer-repo/scrutinizer-www, branchmaster. A push tomasterdeploys to GitHub Pages through.github/workflows/deploy.yml(see that repo'sDEPLOY.md). - Pushes. None on weekdays from 10am to 3pm PT. Every push command below carries the clock check in the same command.
1. Pre-flight
cd ~/Documents/dev/scrutinizer-repo/scrutinizer2025
git branch --show-current # expect agent/usability-study-links
git fetch origin
git merge-base --is-ancestor origin/main HEAD && echo "HEAD contains origin/main"
git status --short # note anything that isn't yours; don't stage it
git status --short -- main.js menu-template.js settings-manager.js shared renderer package.json # what the build packages
for k in APPLE_ID APPLE_ID_PASSWORD APPLE_TEAM_ID; do grep -q "^$k=." .env && echo "ok $k" || echo "MISSING $k"; done
node -p 'require("./package.json").version'
git describe --tags --abbrev=0 # previous release tag
[ -d node_modules ] || npm ci
- All three
.envkeys must printok. Without themnpm run buildfails at notarization. - If HEAD doesn't contain
origin/main, stop and ask. Something was pushed tomainthat this checkout doesn't have, and this file may be out of date too: readgit show origin/main:.claude/skills/release/SKILL.md. If the checkout is only behind and holds someone else's WIP, don't pull or rebase it; use step 1b. - If the second
git statuslists a change that isn't part of this release, the build would package it. Don't build here; use step 1b. - Settle the target version and the release type with Andy.
- List what ships:
git log vPREV..HEAD --oneline. - If
docs/release_notes_vX.Y.Z.mdalready exists, read it before writing anything. It may be a draft for other, unreleased work. v2.8.1 found an unreleased Study Links draft there. Move such a draft aside, e.g. todocs/release_notes_<topic>_draft.md, after Andy agrees. - Public prose announces only what Andy has cleared. As of 2026-10-20, Study Links aren't announced in release bodies or blog posts. A fixed bug gets one plain sentence, without before/after or mechanism.
1b. Release from a worktree (when the main checkout isn't clean)
MAIN=~/Documents/dev/scrutinizer-repo/scrutinizer2025
WT=~/Documents/dev/scrutinizer-repo/scrutinizer2025-release-X.Y.Z
git -C "$MAIN" fetch origin
git -C "$MAIN" worktree add -b release/vX.Y.Z "$WT" origin/main
ln -s "$MAIN/.env" "$WT/.env" # gitignored; signing and notarization read it through the link
cd "$WT" && npm ci
test -f node_modules/electron/path.txt && node_modules/.bin/electron --version || echo "ELECTRON NOT INSTALLED"
- Run the
.envkey check from step 1 again in$WT, then do every later step there. The release commit lands onrelease/vX.Y.Z; step 7 pushes the sha, so the branch name doesn't matter. - Leave the main checkout's branch and WIP alone. Whoever owns the WIP rebases onto the release commit.
npm cican leave Electron unextracted. On 2026-10-31 (Electron 30.5.1, Node 26.8) it exited 0 withnode_modules/electron/distholding onlyLICENSE,LICENSES.chromium.htmlandversion, and nopath.txt. Rerunningnode node_modules/electron/install.jsdid nothing, andnpm testfailed with "Electron failed to install correctly". Unpack the cached zip by hand, after its sha256 matches:
V=$(node -p 'require("./node_modules/electron/package.json").version')
ZIP=$(ls ~/Library/Caches/electron/*/electron-v${V}-darwin-arm64.zip | head -1)
if [ "$(shasum -a 256 "$ZIP" | cut -d' ' -f1)" = "$(node -p "require('./node_modules/electron/checksums.json')['electron-v${V}-darwin-arm64.zip']")" ]; then
ditto -x -k "$ZIP" node_modules/electron/dist && printf 'Electron.app/Contents/MacOS/Electron' > node_modules/electron/path.txt && node_modules/.bin/electron --version
else echo "STOP: no cached zip, or its checksum doesn't match"; fi
npm run build isn't affected: electron-builder downloads its own copy.
- Once step 9 passes, remove the worktree with
git -C "$MAIN" worktree remove "$WT".
For silent, skip to step 4.
2. Version, changelog, roadmap, README, release notes
package.json: edit theversionfield directly. Don't usenpm version, because it commits and tags on its own terms.CHANGELOG.md: add## [X.Y.Z] - YYYY-MM-DDin Keep-a-Changelog form.tests/unit/release-version-tag-sync.test.jsfails without this heading.ROADMAP.md: add### vX.Y.Z: <Title> (YYYY-MM-DD)at the top of## Release history, with one or two bullets. For a major release, also move finished items out of "Next".README.md: update themacOS Installer:line near the top and the### Download (vX.Y.Z)section.docs/release_notes_vX.Y.Z.md:- Major: full notes, following earlier
docs/release_notes_v*.md. - Dot: a condensed version of the CHANGELOG entry.
- Major: full notes, following earlier
3. Commit and tag locally
git add package.json CHANGELOG.md ROADMAP.md README.md docs/release_notes_vX.Y.Z.md
git commit -m "release: vX.Y.Z — <brief summary>"
git tag -a vX.Y.Z -m "vX.Y.Z"
- Tag before
npm test.release-version-tag-sync.test.jsneeds avX.Y.Ztag to exist. - Release tags are annotated.
- If the release commit is amended, move the tag before anything is pushed:
git tag -f -a vX.Y.Z -m "vX.Y.Z". - Don't push yet.
4. Tests and gates
npm test # unit, visual, memory, integration
npm run check:scroll # continuous-scroll HUD gate (launches the app)
npm run check:study && npm run check:study -- --dpr=1 # recorded study end to end, at 2x and 1x
node scripts/validate-color-search.js
git diff --stat tests/validation/reports/color-search-report.md
npm testmust pass.npm run check:scrollmust exit 0. It is the only check that watches the HUD while the page moves, and a failure stops the release.npm run check:studymust exit 0 at the display's own DPR and at--dpr=1. It runs a two-task recorded study in the app and admits the saved session with the Workbench's checks; a failure stops the release. Recorded studies were broken on 2x displays in 2.8.0 through 2.8.2 because the
Content truncated.
When not to use it
- →When releasing a non-Electron application.
- →When the application is not Scrutinizer.
- →When not using GitHub for releases or website hosting.
Prerequisites
Limitations
- →The skill builds only ARM64 architecture.
- →It requires a single `package.json` at the root.
- →It relies on GitHub Releases for auto-update functionality.
How it compares
This skill automates a specific Electron application release process with integrated golden captures and website updates, unlike manual or generic release workflows.
Compared to similar skills
release side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| release (this skill) | 0 | 8mo | Review | Advanced |
| flow-nexus-platform | 6 | 8mo | Review | Beginner |
| perf-lighthouse | 13 | 8mo | Review | Intermediate |
| netlify-deploy | 7 | 9mo | Review | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
You might also like
flow-nexus-platform
ruvnet
Comprehensive Flow Nexus platform management - authentication, sandboxes, app deployment, payments, and challenges
perf-lighthouse
tech-leads-club
Run Lighthouse audits locally via CLI or Node API, parse and interpret reports, set performance budgets. Use when measuring site performance, understanding Lighthouse scores, setting up budgets, or integrating audits into CI. Triggers on: lighthouse, run lighthouse, lighthouse score, performance audit, performance budget.
netlify-deploy
openai
Deploy web projects to Netlify using the Netlify CLI (`npx netlify`). Use when the user asks to deploy, host, publish, or link a site/repo on Netlify, including preview and production deploys.
azure-static-web-apps
github
Helps create, configure, and deploy Azure Static Web Apps using the SWA CLI. Use when deploying static sites to Azure, setting up SWA local development, configuring staticwebapp.config.json, adding Azure Functions APIs to SWA, or setting up GitHub Actions CI/CD for Static Web Apps.
smoke-test
mastra-ai
Create a Mastra project using create-mastra and smoke test the studio in Chrome
web-development
TencentCloudBase
Web frontend project development rules. Use this skill when developing web frontend pages, deploying static hosting, and integrating CloudBase Web SDK.