agentleFS
Sign inStart free
Zwin-uxZwin-ux/kit/.claude/skills/kit-release/SKILL.md

kit-release

Skill0 starsChanged 13 days agoMITView on GitHub

Prepare and ship a Kit release (vX.Y.Z) to the GitHub Release, npm and crates.io. Use when asked to cut, bump, tag or check a Kit release, or to read a failed Release npm run.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

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

    Never print or echo NPM_TOKEN or CARGO_REGISTRY_TOKEN.

    line 17
  2. Very specific:

    Update the date and release line in docs/dev/CURRENT.md.

    line 26

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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

Kit release

The full procedure is docs/dev/RELEASING.md. This is the short path and the rules that keep it safe. Its "Ship day" list was written for 2.0.0: for any later release, skip its steps 3 and 4 (the Zwin-ux/kits index repo already exists; rebuild the index only when a kit in crates/kit-cli/kits/ changed) and read every 2.0.0 there as the new version.

Rules

  • The owner (Mazen) pushes the tag. A tag push publishes to npm, crates.io and the GitHub Release, and npm and crates.io versions can never be reused. Prepare everything, then ask. Never tag, never run Release npm with publish checked, never npm publish or cargo publish by hand.
  • Never print or echo NPM_TOKEN or CARGO_REGISTRY_TOKEN. gh secret list -R Zwin-ux/kit shows the names and dates only, and that is all you need.
  • main must be green on Ubuntu, macOS and Windows (rust.yml) at the commit that gets the tag.

The bump PR

  1. Branch from main: git switch -c release/vX.Y.Z origin/main.
  2. node scripts/version.mjs --set X.Y.Z, then cargo update -w, then node scripts/version.mjs --check.
  3. In CHANGELOG.md, rename ## Unreleased to ## X.Y.Z — <title>. The release fails without it.
  4. node scripts/release-notes.mjs X.Y.Z and read the notes it prints.
  5. Update the date and release line in docs/dev/CURRENT.md.
  6. Push, open the PR, wait for rust.yml on all three OSes and the crates.io package job.

Optional dry run of the whole pipeline (publishes nothing): Actions → Release npm → Run workflow on the PR branch with publish unchecked.

After the owner merges and tags

Watch release-npm.yml to the end: build → verify → github-release → publish → npm-check, crates-io, install-check. Then confirm from outside:

npm view @mzwin/kit dist-tags                     # latest = X.Y.Z (a prerelease moves only its own tag)
curl -s -A kit-check https://crates.io/api/v1/crates/kitctl | python -I -c "import json,sys;print(json.load(sys.stdin)['crate']['max_version'])"
gh release view vX.Y.Z -R Zwin-ux/kit

A rerun of a failed job skips what is already published (gh run rerun <id> -R Zwin-ux/kit --failed). Report which of the three channels you saw with your own command, not from the run summary alone.

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.

Check your setup, free