release
Skill6 starsChanged 10 days agoApache-2.0View on GitHub
Publishes a new release of Snotra Agent: bumps the version in package.json through a pull request, then creates the git tag vX.Y.Z and pushes it, which makes the GitHub Actions pipeline (.github/workflows/release.yml) build the macOS, Windows and Linux artifacts and publish the release. Triggers on sentences like "erstelle ein Release", "erstell ein neues Release", "Release erstellen", "mach ein Release", "neues Release", "Version veröffentlichen", "release this", "cut a release", "create a release", "publish a new version". Only makes sense in this repository (snotra).
- Reads credentials
- Commits and pushes
193 other projects use a version of this.
Adopted by
Most recently taken up by
- bpatrik/pigallery2their own version, first seen Nov 16, 2026
- Shasnow/StarRailAssistanttheir own version, first seen Nov 16, 2026
- CoreBunch/Instatictheir own version, first seen Nov 16, 2026
- coredevices/PebbleOStheir own version, first seen Nov 16, 2026
- eugene1g/agent-safehousetheir own version, first seen Nov 12, 2026
- BlockRunAI/ClawRoutertheir own version, first seen Nov 11, 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
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 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
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
rivet-devSkilllaunch-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
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 repository3 other files it gives its agents.
- installSkill
- parallel-tasksSkill
- user-feedbackSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 43
When it's unclear, ask briefly.
- Distinctive: line 48
Run these in order and stop with a clear message when something doesn't fit:
- Distinctive: line 87
Keep only what a user notices: a new feature, a changed label, default or behaviour, a bug they could run into that is fixed now.
- Distinctive: line 91
Write one bullet per point, from the user's side and in their words —
- Very specific: line 96
Write it in English first, then the German version with the same content, addressing the reader as *du*.
- Very specific: line 106
Read the current version from package.json (node -p "require('./package.json').version") and name the version that results from the chosen …
- Distinctive: line 117
Only continue after agreement.
- Very specific: line 165
Only the tag ref is pushed — no git push origin main, that state is already there through the merge.
- Distinctive: line 169
If GitHub rejects the push because it aimed at main, something went wrong — since the bypass was removed (#240) there is no way through for …
- Distinctive: line 216
Don't upload additional assets by hand.
“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
Cut a release
This skill publishes a new version by pushing a v* tag. Building and uploading
the artifacts is the pipeline's job
(.github/workflows/release.yml). The background and the manual procedure are
in docs/release/release.md, the flow as a diagram in
docs/release/release-flow.svg.
Important: a pushed tag triggers a public GitHub release — that is outward-facing and not trivial to undo. So get one explicit confirmation of the target version before pushing the tag.
Just as important: the version commit goes through a pull request, not
straight onto main. npm version without --no-git-tag-version would commit
to the current branch — which during a release means main, which only gets
through with a ruleset bypass and contradicts
git-workflow.md (issue #238). Since #240 nobody
is left in bypass_actors — so a direct push is rejected, not merely logged.
The tag push itself is uncritical: ruleset 23177645 has target: branch and
does not cover tags.
Step 1 — determine the bump type
The default is patch. Derive the type from what the user said:
- "patch" / "bugfix" / nothing said →
patch - "minor" / "new feature" / "feature release" →
minor - "major" / "breaking" / "big release" →
major
When it's unclear, ask briefly; otherwise assume patch. Helpful for judging
it: git log --oneline vX.Y.Z..HEAD since the last tag.
Step 2 — pre-flight checks (stop on failure)
Run these in order and stop with a clear message when something doesn't fit:
- On
main? —git rev-parse --abbrev-ref HEAD. If not, ask the user whether to release from this branch anyway (the pipeline builds from the tagged commit;mainis the usual one). - Working tree clean? —
git status --porcelain. If it isn't empty: stop. Tell the user that uncommitted changes have to be committed or stashed first. - Up to date locally? —
git fetch, then check thatmainisn't behindorigin/main. If it is, advise agit pull. - Tests green? —
npm testandnpm run test:e2e. On a red test, stop and show the output.
Step 2a — user manual report (reports, does not stop)
node scripts/manual-upkeep-report.jsIt lists the pull requests since the last release tag that changed
user-visible code (src/, system-skills/) without touching manual/ and
without ticking User manual not affected in their description, and the ones
that changed the UI. Show both lists to the user together with the version
question in step 3 — a missing manual page is fixed in a pull request of its
own before the tag, or consciously left for later; a UI change means
cd manual && npm run screenshots for the motifs it touches. Neither stops
the release. The rule behind it:
user-manual.md.
Step 2b — draft the notes for the user
The update dialog shows only a section written for the user, not GitHub's generated list (#1072, background in docs/release/release.md). Draft it now, so it is confirmed together with the version:
- Go through the pull requests since the last tag
(
git log --first-parent --format=%s vX.Y.Z..HEAD); the report from step 2a already tells the internal ones apart. Read the description of each one that changedsrc/orsystem-skills/(gh pr view <N> --json body). - Keep only what a user notices: a new feature, a changed label, default or behaviour, a bug they could run into that is fixed now. Leave out tests, CI, refactorings, documentation, rules and skills of this repository, the manual's screenshots, and fixes for something no release ever shipped.
- Write one bullet per point, from the user's side and in their words —
bold lead sentence, then at most one or two sentences on what to do or
expect. No issue or pull request numbers, no file names, no internal terms.
A step the user has to take, or a version they cannot go back from, goes
into a quoted paragraph (
> **…**) above the bullets. - Write it in English first, then the German version with the same
content, addressing the reader as du. Save both in the scratchpad as
notes.en.mdandnotes.de.md. - Nothing for the user? Then one sentence each, e.g. This version improves Snotra behind the scenes; nothing changes in how you use it. / Diese Version verbessert Snotra im Hintergrund; an der Bedienung ändert sich nichts.
Step 3 — compute the target version and confirm it
Read the current version from package.json
(node -p "require('./package.json').version") and name the version that
results from the chosen bump. Then have it confirmed, for example:
"Currently 1.0.0 → new release v1.0.1 (patch). The bump goes through a pull request, after which it is tagged and a public release is published. Proceed?"
Show the drafted notes for the user from step 2b in the same message, both languages, and take corrections before going on.
Only continue after agreement.
Step 4 — the bump on a branch of its own (local, reversible)
git switch -c release/vX.Y.Z
npm version <patch|minor|major> --no-git-tag-version
git commit -am "vX.Y.Z"
git push origin release/vX.Y.Z--no-git-tag-version is the crucial part: with it, npm version only changes
package.json and package-lock.json and creates neither a commit nor a
tag. The commit holds exactly those two files and nothing else.
Step 5 — pull request and required checks
gh pr create --title "Release vX.Y.Z" --body "…"The release pull request closes no issue, so it needs no Closes #N. Wait until
the three required checks Tests (macos-15), Tests (windows-latest) and
Tests (ubuntu-latest) are green:
gh pr checks --watchRed means: don't merge, fix the cause, push again.
Step 6 — merge and fetch main
gh pr merge --squash --delete-branch
git switch main && git pull
node -p "require('./package.json').version" # has to show X.Y.ZThat last line is the check that the tag is about to point at the right state.
Step 7 — tag and push (the point of no return)
git tag vX.Y.Z
git push origin vX.Y.ZOnly the tag ref is pushed — no git push origin main, that state is
already there through the merge. Pushing over SSH needs
dangerouslyDisableSandbox: true (read access to ~/.ssh/known_hosts).
If GitHub rejects the push because it aimed at main, something went wrong —
since the bypass was removed (#240) there is no way through for that any more.
Report it, don't work around it.
Step 8 — watch the pipeline and report the result
gh run list --workflow=release.yml --limit 1
gh run watch <RUN_ID> --exit-statusOnce it succeeds, name the release link:
gh release view vX.Y.Z --json url,assets -q '.url, (.assets[].name)'On a red run, name the failed jobs and point to
gh run view <RUN_ID> --log-failed. The tag stays in place in that case; pushing
the same tag again does not rebuild automatically — then settle with the user
whether the tag and release are deleted and re-tagged after a fix.
Step 9 — put the notes for the user on top of the release
Once the release exists, write the confirmed section from step 2b into it:
node scripts/release-user-notes.js vX.Y.Z --en <scratchpad>/notes.en.md --de <scratchpad>/notes.de.mdUntil then the update dialog offers the new version without a notes box. Check the result on the release page: both languages above What's Changed, no markers visible. A correction later is the same command again — it replaces the section.
Notes
- Versioning has its single source of truth in
package.json; the pipeline only builds, it does not tag. The app comparesapp.getVersion()(that is,package.json) against thelatestrelease — which is why the tagged commit has to carry the matching version. - The macOS app and DMG are signed with a Developer ID and notarised (#662); the release job fails when Gatekeeper would reject them. Windows is still unsigned (SmartScreen warns), Linux needs no signature.
- The pipeline starts with a test gate (the job
Test-Gate, callingci.yml:npm teston macOS, Windows and Linux). Red there means: no build, no release — reproducenpm testlocally, fix it, tag anew. - Don't upload additional assets by hand; the pipeline does that.
- As long as the bump goes through the pull request, the tests run twice (the
pull request and the test gate). That is intended: the tagged commit passed
the gate before it landed on
main.
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.

