DevOps & cloud · Automation
release-plugin
/release-plugin
Use when cutting a new version release for the squads Claude Code plugin — version bump, tag, or GitHub release.
For whom
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 26.07.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
Use when cutting a new version release for the squads Claude Code plugin — version bump, tag, or GitHub release.
Original author description
Use when cutting a new version release for the squads Claude Code plugin — version bump, tag, or GitHub release.
How it works
- Files that carry the version (all 4, kept in sync)
- Determine bump type
- Steps
- Out of scope
Original SKILL.md headings · 50 lines, 321 words
SKILL.md preview
--- name: release-plugin description: Use when cutting a new version release for the squads Claude Code plugin — version bump, tag, or GitHub release. --- Version-bump-and-ship workflow for **this repo only** — squads is a Claude Code plugin, not an npm package. ## Files that carry the version (all 4, kept in sync) | File | Field | | --------------------------------- | -------------------------------------------- | | `package.json` | `"version"` | | `package-lock.json` | `"version"` | | `.claude-plugin/plugin.json` | `"version"` | | `.claude-plugin/marketplace.json` | `plugins[0].version` (nested, not top-level) | ## Determine bump type ```bash git describe --tags --abbrev=0 # last release tag (fails if no tags yet — then this is the first release; use all commits) git log <last-tag>..HEAD --oneline # commits since then ``` - Any `feat:` commit → **MINOR** - Any `!` or `BREAKING CHANGE` → **MAJOR** - Otherwise (`fix:`, `chore:`, `docs:`, `refactor:`) → **PATCH** ## Steps 1. **Bump** the 3 JSON manifests to the same `<NEW>` version, then sync the lockfile: `npm install --package-lock-only` (rewrites both version fields in `package-lock.json` from `package.json`). 2. **Verify**: ```bash git grep -n "\"version\": \"<NEW>\"" -- package.json .claude-plugin/plugin.json .claude-plugin/marketplace.json # must print exactly 3 lines git grep -n "\"version\": \"<OLD>\"" -- package.json .claude-plugin/plugin.json .claude-plugin/marketplace.json # must print zero git grep -c "\"version\": \"<NEW>\"" -- package-lock.json # must print 2 ``` 3. **Validate**: run exactly `claude plugin validate . --strict` — must pass before committing. 4. **Commit** (stage only the 4 version files): ```bash git add package.json package-lock.json .claude-plugin/plugin.json .claude-plugin/marketplace.json git commit -m "chore: bump version to <NEW>" ``` 5. **Tag**: `git tag -a v<NEW> -m "Version <NEW>"`. 6. **Confirm with the user before pushing** — push is visible to others and not easily reversible. 7. **Push**: `git push origin master && git push origin v<NEW>`. 8. **Release**: `gh release create v<NEW> --title "v<NEW>" --notes "<notes>"`, notes summarizing the commits since `<last-tag>` grouped by fix/feat/etc. `gh release view v<NEW>` must print it. 9. **Finalize**: `git status` must show a clean working tree. ## Out of scope - `npm publish` — not npm-distributed. - CHANGELOG.md / changelog-generation script — doesn't exist here.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · j0hanz/squads | 100 | MIT |
| steffen74/agentic-data-science | 100 | MIT |
| SteveGJones/ai-first-sdlc-practices | 100 | MIT |
| max4c/skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version 22c307d88f19 (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
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed. - 100release
Release the scratch CLI or the pi package: bump, tag, GitHub release, CI publishes to npm. Use for "release", "publish", "bump version" or "release candidate". - 100release
Use when cutting a new release of the jdwp-debugging plugin — bumping the user-facing version, writing a CHANGELOG entry, committing, tagging, and pushing. Triggers — "do a release", "ship X.Y.Z", "release the last commits", "bump the version", "tag a 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". - 100release
This skill should be used when the user asks to "release a new version", "bump version", "create release tag", "update release notes", "prepare release", or performs any release-related operation for the simulink-automation-suite plugin. - 100release
Perform a full versioned release — bump version, draft release notes, commit, tag, push, and create the GitHub release page. Reads `.claude/project.yaml` for the project's release-context and version-bump helpers; the skill text is universal, the helpers are project-supplied.…