agentleFS
Sign inStart free
NicholasFlemmerNicholasFlemmer/styx-app/.claude/skills/release/SKILL.md

release

Skill31 starsChanged 2 months agoApache-2.0View on GitHub

Release a new Styx version through CI (styx-app release.yml → draft → publish.yml) and check it end to end.

196 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

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

  • 0

    Common

    Most of the 186 edited versions we read keep these.

  • 0

    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. Very specific:

    If a step fails, fix the cause, bump nothing, and re-run the failed jobs (a draft can be deleted and release.yml re-run for the same …

    line 27
  2. Very specific:

    Only native modules (better-sqlite3, node-pty, @napi-rs/keyring, ssh2) stay external in electron.vite.config.ts.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 186 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

Release

Releases are built and published by CI on the public repo (NicholasFlemmer/styx-app), never from a laptop.

  1. Bump version in apps/desktop/package.json (every release needs a new number; the feed refuses a version it already serves) and land it. mirror.yml pushes it to styx-app's sync branch; sync-pr.yml opens a pull request that merges itself once CI passes (about 35 minutes). Wait for that merge before step 2.
  2. Start the release: gh workflow run release.yml -R NicholasFlemmer/styx-app -f version=X.Y.Z (or push a vX.Y.Z tag to styx-app). verify checks the version, waits for CI on that exact commit to pass, and tags it. Mac (signed + notarized, retried on network errors), Windows and Linux build in parallel; draft attaches every installer and feed file to a draft release.
  3. Review the draft on styx-app › Releases. Only the owner presses Publish release: that is the gate.
  4. Publishing runs publish.yml: the update feed (installers first, feed files last, keyless upload through Workload Identity), a check that all three feeds serve the new version, then the Homebrew cask bump in NicholasFlemmer/homebrew-styx. When it succeeds, site.yml rebuilds and redeploys heystyx.com so its stated version matches (run it by hand after a site-only change).
  5. Check: curl -s https://storage.googleapis.com/styx-desktop-releases/mac/latest-mac.yml | head -1, and an installed copy shows "Update available" within 30 minutes.

If a step fails, fix the cause, bump nothing, and re-run the failed jobs (a draft can be deleted and release.yml re-run for the same version until it is published).

Local builds (debugging only)

pnpm release:preflight, then pnpm package:mac (notarizes with the styx-notary keychain profile) or pnpm -F @styx/desktop package:mac:dir && pnpm -F @styx/desktop package:smoke for an unsigned check. pnpm release:publish still uploads a local release/ folder through the gcloud shim, for emergencies only.

Packaging notes (learned 2026-09-05)

  • Only native modules (better-sqlite3, node-pty, @napi-rs/keyring, ssh2) stay external in electron.vite.config.ts; every other main-process dependency is bundled. A packaged app that require()s ESM-only packages (execa, chokidar) at runtime hangs before app.whenReady.
  • apps/desktop/package.json declares packageManager: pnpm@… so electron-builder resolves the hoisted workspace node_modules; workspace packages are devDependencies (bundled by electron-vite), which keeps Storybook/Jest out of the bundle.
  • Without a signing identity electron-builder ad-hoc signs; never pass CSC_IDENTITY_AUTO_DISCOVERY=false on Apple Silicon (an unsigned bundle inherits a broken Electron signature).
  • Windows installers are named Styx-Setup-<version>.exe (no spaces: GitHub renames spaces in release assets).

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.

Check your setup, free