A release workflow that prepares a dated changelog entry, opens a pull request, waits for it to be merged, and then creates the version tag that starts the release process. A changelog is the project's record of user-visible changes.

Use it to cut a versioned software release, including updating the changelog, preparing the release pull request, waiting for approval, and starting the automated build and publishing pipeline.

It removes the need to coordinate these release steps manually while keeping one human check: reviewing and merging the changelog pull request.

How SolaceProducts/solace-broker-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to SolaceProducts/solace-broker-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/SolaceProducts/solace-broker-mcp/main/.claude/skills/cut-release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/SolaceProducts/solace-broker-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/solaceproducts/solace-broker-mcp/cut-release/github.svg)](https://agentmods.dev/skills/solaceproducts/solace-broker-mcp/cut-release)

Your own site

<a href="https://agentmods.dev/skills/solaceproducts/solace-broker-mcp/cut-release"><img src="https://agentmods.dev/badge/skills/solaceproducts/solace-broker-mcp/cut-release/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/solaceproducts/solace-broker-mcp/cut-release"><img src="https://agentmods.dev/badge/skills/solaceproducts/solace-broker-mcp/cut-release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 98 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 5,520 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00098	$0.05520
Opus 5.5	$0.00039	$0.02208
Sonnet 5.5	$0.00020	$0.01104
Haiku 4.5	$0.00010	$0.00552

Measured 22d ago against content hash 247ec0ce0b5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

cut-release scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 22d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/skills/cut-release/SKILL.md · 304 lines

How it starts

The opening of the file, as written. The whole thing — 304 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Cut a release

Run the whole release from one command. Invoked with /cut-release <version> (or "cut a new v0.6.0 release").

The release pipeline (.github/workflows/release.yml) triggers on a pushed v* tag and does the heavy lifting itself — builds binaries for 4 OS/arch, runs the LLM eval suite against the tagged commit, and does not push the multi-arch image or create the GitHub Release until that suite passes. It extracts the tagged commit's ## [X.Y.Z] CHANGELOG block and attaches artifacts + checksums. No GitHub-UI "draft release / auto-generate notes" step is needed. The suite starts beside the build, not after it. A full run costs API credits (about $4.78 when measured on 2026-08-05) and does not retry. A red suite is gh run rerun <run-id> --failed. A full rerun starts the suite again. A missing or rotated key is fixed in repo settings and then that same rerun, not a new tag. There is no admin skip. RELEASING.md has the job graph. A finished binary build is not "clear to publish." So cutting a release reduces to: get the dated CHANGELOG block onto main, then push the tag.

The one human checkpoint is merging the changelog PR — that is where "make sure the changelog is updated properly" happens, and it is required because main is protected and the pipeline reads the CHANGELOG from the tagged commit. Everything before and after is automatic: the merge is treated as the go-ahead, and the tag fires on merge (guarded — see Phase D).

Usage

/cut-release <version> — e.g. /cut-release 0.6.0 or v0.6.0.

Validate first: reject anything not matching ^v?[0-9]+\.[0-9]+\.[0-9]+$ (stable SemVer) before any command uses the value. Then normalize once and derive both forms explicitly: strip a leading v for the bare form (0.6.0) used in the ## [0.6.0] heading and wherever the Phase D awk takes v="0.6.0"; keep the v-prefixed form (v0.6.0) for the git tag and compare-URL segments. Never pass the raw argument through un-normalized (a v0.6.0 input must not yield ## [v0.6.0] or a vv0.6.0 tag).

Read the full file on GitHub · 304 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

22d ago Changed 247ec0ce0b5b
1mo ago Changed 3e467c560de5
1mo ago Changed · +6 lines 1acfa521c9d0
1mo ago Changed f68daa23ff3a
2mo ago First seen · 298 lines · 98 tokens per session scan A 9eba553713e4

Subscribe to this mod's changes

cut-release is a skill published in the GitHub repository SolaceProducts/solace-broker-mcp (18 stars, last pushed yesterday), licensed Apache-2.0. It adds 98 tokens to every session and 5,520 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Releases ai-agents go mcp solace

cut-release next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
cut-releaseSolaceProducts/solace-broker-mcp	Skill	18	yesterday	Apache-2.0	A	98	Claude Code
conventional-gitHarmeet10000/skills	Skill	7	6mo ago	MIT	A	77	Claude Code
octocatHarmeet10000/skills	Skill	7	6mo ago	MIT	A	100	Claude Code, Codex
releasethedotmack/claude-mem	Skill	114k	yesterday	Apache-2.0	A	13	Claude Code
release-notesphuryn/pm-skills	Skill	28k	8d ago	MIT	A	57	Claude Code
multi-agent-release-managerchromium/chromium	Skill	25k	yesterday	BSD-3-Clause	A	27	Claude Code, Codex
pack-submitaeonfun/aeon	Skill	788	yesterday	MIT	A	27	Claude Code, Codex

solace-broker-mcp: Skill for Claude Code