release
Skill25 starsChanged 25 days agoMITView on GitHub
Release a new version of spotnote and spotnote-mcp to npm. Bumps both package.json versions, waits for CI, Test and E2E on main, pushes the tag, and checks the release workflow and npm. Use when the user asks to release, publish or cut a new version.
- Commits and pushes
196 other projects use a version of this.
Adopted by
Most recently taken up by
- zxcvbn-ts/zxcvbntheir own version, first seen Nov 9, 2026
- TechbeeAT/jtxBoardtheir own version, first seen Nov 9, 2026
- ddnexus/pagytheir own version, first seen Nov 9, 2026
- zerx-lab/FluxDowntheir own version, first seen Nov 9, 2026
- orioledb/orioledbtheir own version, first seen Nov 9, 2026
- AmruthPillai/Reactive-Resumetheir own version, first seen Nov 8, 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
- 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 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 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-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 versions196 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 196
- paperclipai/paperclip★ 112ksame name
- modelcontextprotocol/servers★ 92ksame name
- remotion-dev/remotion★ 72ksame name
- traefik/traefik★ 65ksame name
- usememos/memos★ 64ksame name
- tw93/Pake★ 63ksame name
- AmruthPillai/Reactive-Resume★ 45ksame name
- amruthpillai/reactive-resume★ 45ksame name
- reactive-resume/reactive-resume★ 45ksame name
- Yeachan-Heo/oh-my-claude-sisyphus★ 41ksame name
186 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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- docs-updateSkill
- examples-new-frameworkSkill
- examples-reproSkill
- examples-syncSkill
- spotnote-setupSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 186 edited versions we read keep these.
1
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
- Very specific: line 32
Commit as release: vX.Y.Z (the two package.json files, and package/README.md if it changed), and push main.
- Very specific: line 37
Wait for the CI, Test and E2E runs of that commit, and check all three succeeded:
- Distinctive: line 45
If one fails, stop and show the failure.
“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.
Files
Release
The tag does the publishing: .github/workflows/release.yml runs CI, Test and E2E,
then publishes both packages (trusted publishing, with provenance) and creates
the GitHub release. See "Release" in DEVELOPMENT.md.
1. Check the starting point
git status: onmain, nothing uncommitted. If there are changes, ask whether to commit them first; don't release around them.git fetch && git status: up to date withorigin/main.git log --oneline $(git describe --tags --abbrev=0)..HEAD: there are commits since the last tag. None? Stop: nothing to release.
2. Pick the version
While on 0.x, bump the patch (0.1.5 → 0.1.6) unless the user names a
version. Both packages always get the same one.
3. Bump, commit, push
- Set
"version"inpackage/package.jsonandmcp/package.json. node scripts/readme.mjs: npm's page showspackage/README.md, a copy of the root README (with absolute image paths) made by that script. The release's CI checks it, and won't publish a stale one.pnpm lint && pnpm test.- Commit as
release: vX.Y.Z(the twopackage.jsonfiles, andpackage/README.mdif it changed), and pushmain.
4. Wait for main to pass
Wait for the CI, Test and E2E runs of that commit, and check all three succeeded:
gh run list --branch main --limit 6 --json name,status,conclusion,headSha
gh run watch <id> --exit-statusA run cancelled by a newer push doesn't count: wait for the release commit's own. If one fails, stop and show the failure; don't tag.
5. Tag
git tag vX.Y.Z && git push origin vX.Y.ZThen watch the Release run (gh run list --workflow release.yml --limit 1).
Its release job runs after ci and test pass.
6. Check it's out
- The publish step's log shows
+ spotnote@X.Y.Zand+ spotnote-mcp@X.Y.Z. gh release view vX.Y.Z --json url: the GitHub release exists.npm view spotnote version: npm can take a few minutes to show it. If it still shows the old version, say so; the publish log is the proof.
Report the version, the GitHub release URL, and what's in it (the feat: and
fix: commits since the last tag).
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.