agentleFS
ahmadrosidahmadrosid/nakama/.agents/skills/release/SKILL.md

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

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

  • 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

  • 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

    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

  • parcadeiSkill

    agent-context-isolation

    Agent Context Isolation

    Also in 3 projects that use this

  • +3 more from Grinv

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
  1. Very specific:

    Run every gh call outside the sandbox.

    line 17
  2. Very specific:

    Use a clean checkout of main: If the user's checkout has other work, make a worktree: git worktree add ../nakama-release origin/main.

    line 22
  3. Very specific:

    Check the risk: Read the diff for DB schema or migration changes (packages/db/sql, packages/db/src/adapters), auth and access changes, …

    line 30
  4. Very specific:

    Check CI on the commit you will tag: Every check must pass, including build-images and publish:

    line 34
  5. Distinctive:

    If a check still runs, wait.

    line 40
  6. Distinctive:

    Leave out a group that has no items.

    line 64
  7. Very specific:

    Keep notes.md in the scratchpad, not in the repo.

    line 70
  8. Distinctive:

    Read the "Rollout of X.Y.Z" region: status, "N of N instances updated", and the Detail column.

    line 98
  9. Distinctive:

    Finish: Wait for "Complete" and N of N updated before you report.

    line 108
  10. Distinctive:

    Keep the BrowserOS tabs open.

    line 119

“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 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

  1. 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.
  2. Find the range.
    gh api repos/ahmadrosid/nakama/releases/latest --jq .tag_name
    git log --oneline <last-tag>..origin/main
  3. Check the risk. Read the diff for DB schema or migration changes (packages/db/sql, packages/db/src/adapters), auth and access changes, Dockerfile and .docker/runtime-deps, and old config files that must still load. Tell the user about any behavior change that users will notice.
  4. Check CI on the commit you will tag. Every check must pass, including build-images and publish:
    gh api repos/ahmadrosid/nakama/commits/<sha>/check-runs \
      --jq '.check_runs[] | "\(.name): \(.conclusion // .status)"'
    If a check still runs, wait. If one fails, stop and tell the user.
  5. Bump and tag. Next patch after the latest release. Only root package.json changes. Commit straight to main, 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
  6. 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:
    ## 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).
    Leave out a group that has no items. Leave out docs, tests and refactors.
    gh 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 --latest
    Keep notes.md in the scratchpad, not in the repo.

Part B: production rollout

  1. 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)"'
  2. 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
  3. Roll out in BrowserOS. Load the browseros-neo tools, name_session, then tabs action="new" with https://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.
  4. 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.
  5. 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 shows Nakama X.Y.Z and What's new links to releases/tag/vX.Y.Z. Check any feature in this release that is visible on that page. Take a screenshot.
  6. 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.

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.