release
Skill29 starsChanged 2 months agoMITView on GitHub
Cut a hyalo release end-to-end — verify/bump the workspace version, rotate the changelog with hyalo itself, sync the winget fork, publish the GitHub release with curated + auto-generated notes, and watch the pipeline. Use this skill whenever the user wants to release a new hyalo version, cut/tag/publish vX.Y.Z, says /release, or says things like "ship 0.19.0", "cut the release", or "publish the release".
- Installs packages
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- naomiaro/waveform-playlisttheir own version, first seen Nov 16, 2026
- osmlab/name-suggestion-indextheir own version, first seen Nov 16, 2026
- vulnerability-lookup/vulnerability-lookuptheir own version, first seen Nov 16, 2026
- ClickHouse/mcp-clickhousetheir own version, first seen Nov 16, 2026
- bpatrik/pigallery2their own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 2026
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.
MicrosoftSkillcreate-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
GrinvSkillchangelog-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
Microsoft AzureSkillcomponent-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
GrinvSkilldocs-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 AzureSkilldocumentation-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
parcadeiSkillagent-context-isolation
Agent Context Isolation
Also in 3 projects that use this
- +3 more from Grinv
Other versions193 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 193
- paperclipai/paperclip★ 114ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 73ksame name
- traefik/traefik★ 66ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 64ksame name
- AmruthPillai/Reactive-Resume★ 46ksame name
- amruthpillai/reactive-resume★ 46ksame name
- reactive-resume/reactive-resume★ 46ksame name
- Yeachan-Heo/oh-my-claudecode★ 41ksame name
183 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- dogfoodSkill
- review-rustSkill
- security-auditSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
NEVER create git tags manually.
- Very specific: line 23
Every hyalo invocation below means target/release/hyalo (build it first if stale).
- Very specific: line 68
Check the root Cargo.toml.
- Very specific: line 75
Every other file that carries the version must match too — the xtask gates fail otherwise.
- Very specific: line 95
If a bump is needed: edit the three fields, run cargo build --release (refreshes Cargo.lock — commit it too), run the full gates (cargo fmt …
- Very specific: line 170
Verify all eight npm packages reached the target version, then dispatch gh workflow run npm-registry.yml -f version=X.Y.Z to test …
- Distinctive: line 181
Do NOT bump the workspace version for the next cycle automatically.
“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.
Files
Release hyalo
Cuts a release vX.Y.Z from main. The GitHub Release publish event is
what triggers the build/package pipeline (.github/workflows/release.yml,
shared via ractive/release-workflows) — so the release is created last,
after everything on main is final.
Hard rules
- NEVER create git tags manually.
gh release createmakes the tag. - CI enforces tag == workspace
Cargo.tomlversion; mismatch fails the pipeline after the tag exists — check the version BEFORE releasing. - Everything lands on
mainbefore the release is created.mainis protected (a direct push is declined, seen on 0.26.0), so the mechanical release commits (version bump, changelog rotation) go on arelease/vX.Y.Zbranch and merge through one PR with green CI. Create the release only after that PR is merged. - Every
hyaloinvocation below meanstarget/release/hyalo(build it first if stale). The barehyaloon PATH is the previously installed release — it predates the version being cut and will reject new config keys/flags (v0.18.0 example: it choked on[changelog]in.hyalo.tomland didn't knowlint --profile).
1. Preconditions
Decide the version from the [Unreleased] contents (pre-1.0 convention
here: minor bump for features/breaking, patch for fix-only). Check published
versions across channels before choosing it: gh release list --limit 5 and
npm view @ractive-ch/hyalo versions --json, plus the target versions of the
npm platform packages and crates when publishing those. A missing GitHub tag
does not mean the version is unused. If a channel already published that
version from older source, choose a fresh version for the new changes across
channels; immutable package versions cannot be replaced. Completing a partial
release at an existing version is only appropriate for the same source and
artifacts, using the publication workflow's existing-version checks.
The 2026-09-13 dogfood found exactly this split: GitHub's latest was 0.21.0,
npm already shipped 0.23.0, and CHANGELOG.md had both a dated [0.23.0]
section and substantial [Unreleased] content. Releasing the new work therefore
needs a new version (0.24.0 for the current feature-bearing changes), preserving
the existing 0.23.0 history. Recheck registry state when actually releasing.
Then run the read-only preflight — it checks branch/clean/sync, the 3-spot version match, that the tag doesn't exist, the changelog state (pre- vs post-rotation), changelog-profile lint, and gh auth:
.claude/skills/release/scripts/release-preflight.sh check X.Y.ZFix every FAIL before proceeding. Additionally verify the latest merges are
green (gh run list --branch main --limit 5 / gh pr checks <last-PR>) —
the script cannot judge CI health. It also does not check registry versions,
and accepts an existing changelog section even when [Unreleased] is non-empty.
A passing preflight therefore does not establish that the version is available
or the changelog is fully rotated. Preview hyalo changelog release X.Y.Z
--dry-run when rotation is still needed; an existing version section is a
reason to reconcile the version/history, not delete published history to make
the command pass.
2. Verify or bump the workspace version
Check the root Cargo.toml. The version appears in three places that
must all match the target:
[workspace.package] version = "X.Y.Z"hyalo-core = { path = ..., version = "X.Y.Z" }hyalo-mdlint = { path = ..., version = "X.Y.Z" }
Every other file that carries the version must match too — the xtask gates
fail otherwise. The full set is 17 files: Cargo.toml, Cargo.lock,
fuzz/Cargo.lock (its own workspace; CI's fuzz-compile runs cargo check
--locked, so refresh it with cargo update -p hyalo-core --offline
--manifest-path fuzz/Cargo.toml; missed on 0.26.0 and caught in review), root
package.json, pi-package/package.json, the vendored
crates/hyalo-cli/templates/pi/package.json,
plugins/hyalo/.codex-plugin/plugin.json, npm/hyalo/package.json,
npm/hyalo/package-lock.json, the seven npm/platforms/*/package.json, and
.github/workflows/npm-registry.yml (its default version input). Run
./target/debug/xtask generate-npm-packages --generate (build xtask first) to
rewrite the npm manifests and the lockfile lines; it drops the lockfile
integrity of the platform entries it moves, so after the npm job publishes,
delete the seven node_modules/@ractive-ch/hyalo-* entries from
npm/hyalo/package-lock.json, run npm install --package-lock-only in
npm/hyalo (without the delete, npm keeps the hash-less entries) and commit
the lockfile with the hashes. docs/releasing.md has the table.
Often the bump already happened during the dev cycle (e.g. 0.18.0 was bumped
in the changelog-conversion PR long before release day) — then just verify.
If a bump is needed: edit the three fields, run cargo build --release
(refreshes Cargo.lock — commit it too), run the full gates
(cargo fmt → cargo clippy --workspace --all-targets -- -D warnings →
cargo test --workspace -q), commit on the release/vX.Y.Z branch:
chore(release): bump version to X.Y.Z.
3. Rotate the changelog (dogfood it)
target/release/hyalo changelog release X.Y.Z --apply
target/release/hyalo lint --dir . CHANGELOG.md --profile changelog # root file is outside the vault → needs --dir .This moves [Unreleased] into a dated ## [X.Y.Z] section and rewrites the
footer compare-links. Lint must report 0 errors. Commit on the release branch:
docs(changelog): release X.Y.Z. Push the branch, open the PR
(chore(release): X.Y.Z), and merge it with
gh pr merge N --merge --delete-branch --match-head-commit <sha> once CI is
green. Then pull main before the steps below.
4. Sync the winget fork
gh repo sync ractive/winget-pkgsA stale fork makes the pipeline's winget submission fail with a misleading
CreateRef error — sync every time, before the release exists.
4b. Dry-run the release pipeline
gh workflow run release.yml --ref main
gh run list --workflow release.yml --limit 1 # then: gh run watch <id>With every input left at its default, a workflow_dispatch run builds and
tests every target, including the musl tests that run through cross's
/qemu-runner and that PR CI never runs, and only dry-runs publishing
(dry-run-summary). Create the release only after it is green. On 0.26.0 a
published release failed in the musl build (five tests took the runner for
hyalo; PR #426 runs the binary directly), was left as an assetless "Latest" that the
setup-hyalo CI step installs, and had to be deleted and re-cut.
5. Create the release (curated notes + auto-notes)
Extract the freshly rotated section as the human-curated top of the release
notes, then create the release. GitHub prepends --notes-file to the
--generate-notes PR list (grouping per .github/release.yml labels;
unlabeled PRs land under "Other Changes").
.claude/skills/release/scripts/release-preflight.sh notes X.Y.Z > /tmp/relnotes.md
gh release create vX.Y.Z --notes-file /tmp/relnotes.md --generate-notesThe notes mode fails loudly (exit 1) if the [X.Y.Z] section is missing
or empty — never publish with an empty notes file. (If hyalo changelog
show <version> exists by now, prefer it.)
6. Watch the pipeline and verify
gh run list --workflow release.yml --limit 1thengh run watch <id>— all jobs green (multi-OS builds, musl statics, deb/rpm → Cloudsmith, Homebrew, winget, SBOMs, provenance, SHA256SUMS).gh release view vX.Y.Z— assets present, notes render with the curated section on top.- Verify crates publication. The shared release workflow at
v0.2.0publishes the configured crates automatically through itscrates-iojob. Confirm that job passes and all three target versions exist on crates.io.publish-crates.ymlis the manual recovery path, not an additional mandatory publication: if recovery is needed, dispatchgh workflow run publish-crates.yml -f ref=vX.Y.Z, find its run withgh run list --workflow publish-crates.yml --limit 1, and watch it to success. Inspect that workflow before recovering a partially published release. - Verify all eight npm packages reached the target version, then dispatch
gh workflow run npm-registry.yml -f version=X.Y.Zto test installation from the registry on macOS, Linux, Windows and Alpine/musl. - Pipeline internals live in
ractive/release-workflows; failures inside reusable jobs are usually fixed there, not here.
7. Post-release follow-ups
- Downstream consumers pinned to "next release" features (e.g. the
ractive/setup-hyaloaction's smoke fixtures) can now be unblocked — check for release-blocked TODOs before closing out. - Do NOT bump the workspace version for the next cycle automatically; that happens when the next cycle actually starts.
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
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.

