agentleFS
enes-alatasenes-alatas/spool/.claude/skills/release/SKILL.md

release

Skill48 starsChanged 2 days agoApache-2.0View on GitHub

Use when tagging a Spool release, writing its notes, or working out which build a binary or a bug report names.

  • Commits and pushes

193 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

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 183 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Is main releasable today?: Run git fetch --tags origin && bash scripts/release-gate.sh (it needs gh signed in and jq).

    line 68

“Common” is measured: kept by at least 6 in 10 of the 183 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 — tags, release notes and a build's name

Moved verbatim from docs/CONVENTIONS.md (#470), which keeps the one-line rule and points here. The rule binds whether or not this skill is loaded.

Tagging mechanics (#223): the operator tags, never a loop — a tag names what the fleet runs, and only the person who runs it knows when that changed. Two occasions: completing a rung (v0.n+1.0), and on demand when the operator updates the running fleet, so "what the fleet runs" always has a name rather than a merge time. Notes come from the Conventional Commit titles, gh release create <tag> --generate-notes; there is no CHANGELOG file, because a generated list and a hand-kept one disagree eventually and the generated one is the honest half. A release is titled with its tag alone (v0.4.0, #485): the rung a tag completes is on its milestone, not in the name.

When to release, the gate, and who does what on release day are a team decision, kept in docs/CONVENTIONS.md ("Releases", #1452). This skill is how to carry them out.

What a tag builds (ADR-0052, #756): the tag fires release.yml. It refuses a tag whose commit is not on main, and one that would ship a feature half (#1446): a feat PR merged since the last tag whose Other half: names an issue still open (scripts/release-gate.sh). It builds both images on native amd64 and arm64 runners (scripts/release-images.sh), pushes them to ghcr.io/<owner>/spool-workstation and spool-egress as one multi-arch image each, and attests them (#763). Then it runs scripts/release-build.sh with their digests embedded, attests each archive, attaches the archives and SHA256SUMS, and adds the digests to the notes under Images, with the Claude Code version the workstation image pins. That version is docker/workstation/claude-code.version (#1223): to ship a newer CLI, bump it in a PR of its own to one the fleet has run, before the dry run. That PR moves four things together (#1235): the pin file, internal/claude.TestedVersion, fakeclaude's --version line, and the stream-json check on the new build in cmd/fakeclaude/FIDELITY.md. TestTestedVersionIsTheReleasePin fails when the first three disagree. The weekly claude-code-watch workflow files the chore issue that asks for the bump when Anthropic's apt repo serves a newer CLI than the pin, with these and a models.go row per new model as its checklist (#1454). The first release that pushes images creates the two packages: check on the repository's Packages page that both are public, or an operator's docker pull is refused. The workflow creates the release, with generated notes, when a bare git push of the tag left none. Check the run in the Actions tab after tagging: a red one also lands on the ci-health issue. To see what a tag would build first, dispatch release on main. That is a dry run: it builds the images and keeps the archives as a workflow artifact, and pushes and publishes nothing. Its smoke-dry-run job installs those archives and images on a fresh runner and starts a hub on them (scripts/release-smoke.sh, #770).

The green dry run is one of the gate's checks (CONVENTIONS.md, "Releases"). A tag is pushed only on a commit whose dispatched release run, smoke-dry-run included, is green. The tag ask links that run, and the operator checks that the commit it ran on is the commit being tagged. The tag's own smoke then confirms what was published; it is not the first time the binary has been run.

Is main releasable today? Run git fetch --tags origin && bash scripts/release-gate.sh (it needs gh signed in and jq). It lists each feat PR merged since the last tag whose other half is still open, and exits 1 while there is one. The dry run runs the same check first, so ask for the tag only once the gate is green: merge each named half, or close an issue the work no longer needs. An Other half: none — <reason>, API-only or UI-only line passes, so a PR that truly has no other half never holds a tag.

The gate's other checks, run on the commit to be tagged:

  • No open severity:high bug: gh issue list --state open --label severity:high lists none.
  • An upgrade from the last tag: on a fresh Linux machine, a throwaway runner and never the fleet's host, install the last tag the README's way. Then upgrade it from a clone of main, which needs Go and Node on the machine: sudo spool upgrade --dry-run --from-source <clone> main, then the same without --dry-run (OPERATIONS.md, "Upgrade"). It passes when the hub answers at the new version on the same data directory. Elliot (DevSecOps) runs it and sends the run's link to the product owner for the release-day message.

After a tag publishes, its smoke job installs the published release on a fresh runner (scripts/release-smoke.sh <tag>). Not every step is the anonymous one a stranger makes:

  • Anonymous: downloading the archive and SHA256SUMS from the release URL, sha256sum -c, the unpack, the docker pulls from spool images with no registry login (#1580), and the hub's start.
  • With the job's token: gh attestation verify on the archive and both images, which needs a token whatever the visibility.

A red tag smoke means the release is public and broken. Nothing is deleted, and the tag never moves: the attested files and the digests in the notes must keep naming what they named. The steps, in order:

  1. The operator puts a banner at the top of the release notes linking the red run: gh release view vX.Y.Z --json body --jq .body >notes.md, add > **Broken: do not install.** <one line on what failed>, see <run URL>. Use <the last good tag> until the next release. as its first line, then gh release edit vX.Y.Z --notes-file notes.md.
  2. The operator sets it as a pre-release, so releases/latest, which the README's quick start links, moves back to the last good release: gh release edit vX.Y.Z --prerelease. gh release view --json tagName then names the last good release.
  3. The loop that owns the cause fixes it on main through a normal PR. Elliot (DevSecOps) opens the issue from the red run, and reports it on the ci-health issue and in channel fleet.
  4. The operator tags the next release through the gate above. It follows the patch rule in CONVENTIONS.md ("Releases"): vX.Y.(Z+1) when main holds only fixes since vX.Y.Z, and otherwise the next minor. There is no exception for a broken release, since a patch from main would ship the features too. Its green smoke job ends the incident, and the broken release's banner then names the next release.

A build says which Spool it is (#223): git describe --tags --always --dirty is baked in by the Makefile, so a tagged build reports the tag, a build between tags reports its distance from one, and a build from a modified checkout says -dirty. Read it with spool --version, GET /api/version, or the runtime ready startup log. A build that did not go through the Makefile answers from what Go recorded in the binary, and only a build from outside a checkout entirely reports dev — so "dev" in a bug report means the build cannot be identified, not that it is a dev build.

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.