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.zip

Installs 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.
103 chars · catalog descriptionno explicit “when” trigger
Advanced

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

You give it
Git repository with Scrutinizer Electron application
You get back
Signed DMG, ZIP, GitHub release, updated website

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

TypeVersionRelease bodyBlogSite
Majorx.Y.0docs/release_notes_vX.Y.0.mdnew post in scrutinizer-www/src/blog/homepage links, new post
Dotx.y.Z, Z > 0dot-release template (step 8), links the parent postnonehomepage links, parent post's Download section
Silentcurrentunchangednonenone (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)
  • .env in the main checkout with APPLE_ID, APPLE_ID_PASSWORD, APPLE_TEAM_ID
  • gh authenticated with push access to andyed/scrutinizer2025
  • scrutinizer-www cloned at ~/Documents/dev/scrutinizer-repo/scrutinizer-www

Fixed facts

  • Checkout. .env is gitignored and exists only in the main checkout, ~/Documents/dev/scrutinizer-repo/scrutinizer2025. npm run build packages the working tree, not a commit. Release from the main checkout when nothing that ships is modified there; otherwise release from a worktree at origin/main with .env linked in (step 1b). v2.8.2 was released from a worktree.
  • Branches. The checkout lives on agent/usability-study-links. Local main is stale and unused. Don't check it out and don't git push origin main. Releases push the tested sha to both refs/heads/main and refs/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.md holds another session's uncommitted notes.
  • Build. arm64 only, one package.json at the root. npm run build runs scripts/build-signed.js: electron-builder, Developer ID signing, then notarization through scripts/notarize.js (the afterSign hook, 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 reads releases/latest, then latest-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 with Cannot 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 publish config in package.json is provider: 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, branch master. A push to master deploys to GitHub Pages through .github/workflows/deploy.yml (see that repo's DEPLOY.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 .env keys must print ok. Without them npm run build fails at notarization.
  • If HEAD doesn't contain origin/main, stop and ask. Something was pushed to main that this checkout doesn't have, and this file may be out of date too: read git 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 status lists 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.md already 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. to docs/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 .env key check from step 1 again in $WT, then do every later step there. The release commit lands on release/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 ci can leave Electron unextracted. On 2026-10-31 (Electron 30.5.1, Node 26.8) it exited 0 with node_modules/electron/dist holding only LICENSE, LICENSES.chromium.html and version, and no path.txt. Rerunning node node_modules/electron/install.js did nothing, and npm test failed 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 the version field directly. Don't use npm version, because it commits and tags on its own terms.
  • CHANGELOG.md: add ## [X.Y.Z] - YYYY-MM-DD in Keep-a-Changelog form. tests/unit/release-version-tag-sync.test.js fails 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 the macOS 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.

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.js needs a vX.Y.Z tag 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 test must pass.
  • npm run check:scroll must exit 0. It is the only check that watches the HUD while the page moves, and a failure stops the release.
  • npm run check:study must 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

~/Documents/dev/scrutinizer-repo/scrutinizer2025APPLE_IDAPPLE_ID_PASSWORDAPPLE_TEAM_ID

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.

SkillInstallsUpdatedSafetyDifficulty
release (this skill)08moReviewAdvanced
flow-nexus-platform68moReviewBeginner
perf-lighthouse138moReviewIntermediate
netlify-deploy79moReviewBeginner

Try saying

Example prompts that trigger this skill in your AI assistant.

Search skills

Search the agent skills registry