release
Skill826 starsChanged 12 days agoMITView on GitHub
Cut a Nakama release and roll it out to production: check main, bump the patch version, tag, publish GitHub release notes with a user-facing "What's new" section, wait for the Docker image, roll it out on the withnakama.com platform image page in BrowserOS (browseros-neo MCP), and validate on nakama.withnakama.com. Use when the user says /release, "create a release", "cut vX.Y.Z", or "release to production".
- 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 repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adhd-pr-descriptionSkill
- eli5Skill
- plan-reviewSkill
- record-demoSkill
- verify-bsSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 5 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 183 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 17
Run every gh call outside the sandbox.
- Very specific: line 22
Use a clean checkout of
main: If the user's checkout has other work, make a worktree: git worktree add ../nakama-release origin/main. - Very specific: line 30
Check the risk: Read the diff for DB schema or migration changes (packages/db/sql, packages/db/src/adapters), auth and access changes, …
- Very specific: line 34
Check CI on the commit you will tag: Every check must pass, including build-images and publish:
- Distinctive: line 40
If a check still runs, wait.
- Distinctive: line 64
Leave out a group that has no items.
- Very specific: line 70
Keep notes.md in the scratchpad, not in the repo.
- Distinctive: line 98
Read the "Rollout of X.Y.Z" region: status, "N of N instances updated", and the Detail column.
- Distinctive: line 108
Finish: Wait for "Complete" and N of N updated before you report.
- Distinctive: line 119
Keep the BrowserOS tabs open.
“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 Nakama and roll it out
Two parts. Part A makes a GitHub release and its Docker image. Part B puts that image on the hosted platform. Do Part B only when the user asks for production.
Run every gh call outside the sandbox. Prefer gh api (REST) to gh pr /
gh release view --json, which time out here.
Part A: GitHub release
- Use a clean checkout of
main. If the user's checkout has other work, make a worktree:git worktree add ../nakama-release origin/main. Never switch the branch of a checkout that has someone else's changes. - Find the range.
gh api repos/ahmadrosid/nakama/releases/latest --jq .tag_name git log --oneline <last-tag>..origin/main - Check the risk. Read the diff for DB schema or migration changes
(
packages/db/sql,packages/db/src/adapters), auth and access changes,Dockerfileand.docker/runtime-deps, and old config files that must still load. Tell the user about any behavior change that users will notice. - Check CI on the commit you will tag. Every check must pass, including
build-imagesandpublish:
If a check still runs, wait. If one fails, stop and tell the user.gh api repos/ahmadrosid/nakama/commits/<sha>/check-runs \ --jq '.check_runs[] | "\(.name): \(.conclusion // .status)"' - Bump and tag. Next patch after the latest release. Only root
package.jsonchanges. Commit straight tomain, as earlier releases did.sed -i '' 's/"version": "X.Y.Z"/"version": "X.Y.Z+1"/' package.json git commit -m "chore: release vX.Y.Z+1" package.json git push origin main git tag vX.Y.Z+1 && git push origin vX.Y.Z+1 - Write the notes. The account menu item What's new opens
releases/tag/v<running version>, so users read this page. Put a short section for users on top, then the generated list:
Leave out a group that has no items. Leave out docs, tests and refactors.## What's new ### New - **<Feature>.** <One plain sentence on what the user can do> (#PR). ### Changed — please read - **<Change>.** <What works differently, and who it affects> (#PR). ### Fixed - <One line> (#PR).
Keepgh api repos/ahmadrosid/nakama/releases/generate-notes \ -f tag_name=vNEW -f previous_tag_name=vOLD --jq .body >> notes.md gh release create vNEW --title vNEW --notes-file notes.md --latestnotes.mdin the scratchpad, not in the repo.
Part B: production rollout
- Wait for the image. The tag push starts "Docker Publish". Check it at
once and then every minute or two. Do not trust a watcher that says
nothing; read the run state yourself.
gh api "repos/ahmadrosid/nakama/actions/runs?branch=vNEW&per_page=5" \ --jq '.workflow_runs[] | "\(.name) | \(.status) | \(.conclusion)"' - Get the digest. The image tag has no
v. Check the method on the live version first: its digest must match the "Live" row on the page.T=$(curl -s "https://ghcr.io/token?scope=repository:ahmadrosid/nakama:pull" \ | python3 -I -c 'import sys,json;print(json.load(sys.stdin)["token"])') curl -sI -H "Authorization: Bearer $T" \ -H "Accept: application/vnd.oci.image.index.v1+json, application/vnd.docker.distribution.manifest.list.v2+json" \ https://ghcr.io/v2/ahmadrosid/nakama/manifests/X.Y.Z | grep -i docker-content-digest - Roll out in BrowserOS. Load the
browseros-neotools,name_session, thentabs action="new"withhttps://withnakama.com/admin/platform-image.- Fill New image reference with
ghcr.io/ahmadrosid/nakama:X.Y.Z@sha256:<digest>. - Click Roll out image. A dialog asks you to type
ROLLOUT. Type it and click Confirm rollout only when the user asked for production in this conversation.
- Fill New image reference with
- Watch the rollout. The canary (
nakama) goes first, then the rest. Read the "Rollout of X.Y.Z" region: status, "N of N instances updated", and the Detail column. "Host operation ensure is running" and "Waiting for another replacement on this host" are normal. Stop and tell the user if a row says failed or rolled back. - Validate on the canary. In BrowserOS open
https://nakama.withnakama.com/and reload until the canary serves the new version. Open the account menu, and check that the footer showsNakama X.Y.Zand What's new links toreleases/tag/vX.Y.Z. Check any feature in this release that is visible on that page. Take a screenshot. - Finish. Wait for "Complete" and N of N updated before you report.
Roll back
On the platform image page, each older image in Rollout history has a Revert to X.Y.Z button. Use it only when the user asks.
Report
Numbered list, one line each: release URL, image reference, rollout result (N of N, failures), canary checks (pass or fail). Say what you did not check. Keep the BrowserOS tabs open.
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.

