Skip to content
Skills Library
DevOps & cloud · Automation

release

/release

Publish a new version of the account-rotator plugin - pick the version, write its CHANGELOG entry, bump plugin.json, push, tag it with `claude plugin tag`, create the GitHub release, and check that an older install updates to it. Use when asked to release, publish, ship or cut a version.

Licence
MIT
Last repository change
16.10.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 16.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Publish a new version of the account-rotator plugin - pick the version, write its CHANGELOG entry, bump plugin.json, push, tag it with `claude plugin tag`, create the GitHub release, and check that an older install updates to it. Use when asked to release, publish, ship or cut a version.

Original author description

Publish a new version of the account-rotator plugin - pick the version, write its CHANGELOG entry, bump plugin.json, push, tag it with `claude plugin tag`, create the GitHub release, and check that an older install updates to it. Use when asked to release, publish, ship or cut a version.

How it works

  1. 1. Check the tree
  2. 2. Pick the version
  3. 3. Write the changelog entry
  4. 4. Bump and commit
  5. 5. Publish
  6. 6. Check that an older install updates
  7. 7. Say where it is
Original SKILL.md headings · 72 lines, 637 words
SKILL.md preview
---
name: release
description: Publish a new version of the account-rotator plugin - pick the version, write its CHANGELOG entry, bump plugin.json, push, tag it with `claude plugin tag`, create the GitHub release, and check that an older install updates to it. Use when asked to release, publish, ship or cut a version.
---

# Release a version

Claude Code updates an installed plugin only when the `version` in `.claude-plugin/plugin.json` changes. Commits pushed without a bump reach new installs only: everyone who installed earlier stays on the commit they got, and `claude plugin update` tells them "already at the latest version". A release is that bump, with its changelog entry, tag and GitHub release. Bump the version nowhere else.

## 1. Check the tree

- On `main`, not behind `origin`: `git fetch origin && git status -sb`. Commits ahead of it go out with the release.
- Nothing uncommitted. Work another session left uncommitted gets a commit of its own first, with a message that says what it does, never folded into the release commit. If that session is still busy (`ListAgents`), ask the user before committing its work.
- `claude plugin test .` and `claude plugin validate .` pass.

## 2. Pick the version

The last release is `git describe --tags --abbrev=0 --match 'account-rotator--v*'`. Read `git log <last tag>..HEAD` and pick by semver. While below 1.0:

- **minor** (0.2.0 to 0.3.0): new behavior, or anything a user does differently.
- **patch** (0.2.0 to 0.2.1): fixes and wording only.

Going to 1.0.0 is the user's call: ask.

## 3. Write the changelog entry

Add a section at the top of `CHANGELOG.md`, below its intro, headed with the version and the date:

```
## 0.3.0 - 2026-11-02
```

- Bullets with a bold lead-in, in the README's voice: what a user sees or does, not how the code does it. Most important first.
- Leave out refactors, tests, demo tooling and README-only edits, unless the README change is the point (a new way to do something).
- Name things as the panel and README do: **Use now**, **Usage based rotation**, **Connect**.

## 4. Bump and commit

- Set `"version"` in `.claude-plugin/plugin.json`. The entry in `.claude-plugin/marketplace.json` carries no version: keep it that way, or keep the two equal, since `claude plugin tag` refuses when they differ.
- One commit, `Release 0.3.0`, holding the bump and the changelog entry.

Show the user the version and the entry before publishing, unless they already said to go ahead.

## 5. Publish

Write the entry's bullets to a file in the session's scratchpad, then:

```sh
git push origin main
claude plugin tag . --push -m "account-rotator %s"
gh release create account-rotator--v0.3.0 --verify-tag --title "0.3.0" --notes-file <the bullets file>
```

`claude plugin tag` refuses while anything is uncommitted, checks the versions agree, and makes `account-rotator--v<version>`: the tag form Claude Code reads when someone pins a version range. Never move or reuse a tag; a mistake gets a new patch version.

## 6. Check that an older install updates

In a folder in the session's scratchpad, install the previous release from GitHub and update it:

```sh
T=<scratchpad>/release-check; rm -rf "$T"; mkdir -p "$T"
CLAUDE_CONFIG_DIR="$T" claude plugin marketplace add ivokund/claude-account-rotator
M="$T/plugins/marketplaces/claude-account-rotator"
git -C "$M" fetch -q --unshallow --tags; git -C "$M" reset -q --hard <previous tag>
CLAUDE_CONFIG_DIR="$T" claude plugin install account-rotator@claude-account-rotator
CLAUDE_CONFIG_DIR="$T" claude plugin marketplace update claude-account-rotator
CLAUDE_CONFIG_DIR="$T" claude plugin update account-rotator@claude-account-rotator
```

Expect an update to the new version, and its code under `$T/plugins/cache/claude-account-rotator/account-rotator/<version>/`. Pull the marketplace first: `claude plugin update` pulls it only sometimes (not when it was added or pulled moments before). "Already at the latest version" after the pull means the bump didn't reach GitHub: check `plugin.json` on `origin/main`.

## 7. Say where it is

- Users get it as Claude Code starts once they turn on auto-update (in `/plugin`: **Marketplaces**, **claude-account-rotator**, **Enable auto-update**), which is off by default for this marketplace. By hand, they run `claude plugin marketplace update claude-account-rotator`, then `claude plugin update account-rotator@claude-account-rotator`, then start a new session. Say both ways, in release notes too.
- In an issue the release fixes, link the GitHub release and say which version has the fix.

Versions

RepositoryScoreLicence
This page · ivokund/claude-account-rotator100MIT
josephfung/curia100MIT
max-sixty/worktrunk100MIT
gtapps/hermitd100MIT
gtapps/hermitd100MIT
anthony-chaudhary/fak100Apache-2.0
tractorjuice/arc-kit100MIT
drvoss/everything-copilot-cli100MIT
sma1lboy/rove100MIT

Database snapshot: 13.11.2026 · package version e01519fc51ab (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100release-plugin
    Cut a release of this repository - decide the version bump from the changes since the last tag, update plugin.json, CHANGELOG.md and the canvas footer, then tag and publish a GitHub release. Use when skill or canvas changes are ready to reach users, when the user asks to…
  • 100release-this
    Orchestrates the full powerball-harness plugin release with build, validation, version bump, CHANGELOG, tag, and GitHub Release. Use when releasing this plugin.
  • 100release-plugin
    Use when cutting a new version release for the squads Claude Code plugin — version bump, tag, or GitHub release.
  • 100version-release
    Use when bumping version, creating a release tag, or pushing a version tag. Triggers on "version up", "release", "tag push", "bump version".
  • 100ship-release
    Use when the user asks to release, ship, publish, cut or tag a version of a project ("release v0.2.0", "ship a patch", "bump and publish"). Bumps every version manifest, updates CHANGELOG and README badges, commits, lands it directly or through a pull request (pre-PR check,…
  • 100releasing
    Full release lifecycle — version bump, CHANGELOG, rich release notes, tag, publish. Use when user says "release", "tag and release", "publish version", "cut a release", "new version".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.