Skip to content
Skills Library
DevOps & cloud · Automation

release

/release

Cut a release of slinger. Use when the user says "release", "cut a release", "ship X.Y.Z", or "bump the version".

Repository
slinger ↗
Licence
MIT
Last repository change
13.11.2026

Assessment and security

86/ 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.
Content21 / 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 13.11.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

Cut a release of slinger. Use when the user says "release", "cut a release", "ship X.Y.Z", or "bump the version".

Triggers from the description

releasecut a releaseship X.Y.Zbump the version
Original author description

Cut a release of slinger. Use when the user says "release", "cut a release", "ship X.Y.Z", or "bump the version".

How it works

SKILL.md has no level-two headings · 32 lines, 228 words

SKILL.md preview
---
name: release
description: Cut a release of slinger. Use when the user says "release", "cut a release", "ship X.Y.Z", or "bump the version".
---

# Release

CI does the publishing. A release is a version-bump commit on main. When
`.github/workflows/release.yml` sees a version with no tag, it runs the gates,
tags `vX.Y.Z`, and publishes a GitHub release. The release notes are that
version's CHANGELOG section.

1. **Check that it is worth releasing.** `## [Unreleased]` must hold at least
   one change a user can observe. Internal-only changes wait for the next real
   release.
2. **Pick the version.** Default to a patch bump. Use minor for new
   capabilities and major for breaking changes. Before 1.0, use minor for
   breaking changes.
3. **Bump it.**
   - Set `version` under `[workspace.package]` in the root `Cargo.toml`, and the
     same `version` on each path dependency under `[workspace.dependencies]`.
   - Set the same `version` in `plugin/.claude-plugin/plugin.json`: Claude Code
     updates an installed plugin only when this changes. A test fails if it
     differs.
   - Run `cargo update --workspace --offline` to update the lockfile.
4. **Edit the changelog.** Rename `## [Unreleased]` to `## [X.Y.Z] - YYYY-MM-DD`
   and add a fresh, empty `## [Unreleased]` above it. Write the entries for
   users.
5. **Verify.** Run `cargo xtask check-all`. It must be green.
6. **Commit and push.** Commit with `chore(release): X.Y.Z`, then push to
   main.
7. **Confirm.** Watch the run with `gh run watch`, then confirm the release
   with `gh release view vX.Y.Z`.

Never tag by hand. Never let generated notes stand in for the CHANGELOG.

Versions

RepositoryScoreLicence
This page · jayminwest/slinger86MIT
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 ecb2c3189909 (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

  • 100bump-version
    Use when asked to bump the version, prepare or create a release, update the version number, or determine a semantic version increment from recent commits.
  • 100cut-release
    Cut a new agnostic-ai release end to end. Use when the user wants to ship a new version (tag + GitHub Release).
  • 90paw-tools-release
    Automates software releases from version bump to GitHub release. Use when the user requests to 'create a release', 'cut a release', 'publish a new version', or 'prepare a release'.
  • 96making-a-release
    Use when a developer wants to cut, publish, or ship a new release of the CodeScene MCP Server, or asks how to make a release / bump the version.
  • 100pypi-release
    Release a new seckit version to PyPI from this repository. Use when the user asks to publish, release, ship or tag a new version of seckit, bump the version, or check or fix the PyPI publish workflow.
  • 100nvidia-nemoclaw-maintainer-cut-release-tag
    Cut a new semver release — bump all version strings via bump-version.ts, open a release PR, and after merge tag main and push. Use when cutting a release, tagging a version, shipping a build, or preparing a deployment. Trigger keywords - cut tag, release tag, new tag, cut…

Feedback and reports

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