A command for drafting an Unreleased entry in a project’s CHANGELOG.md file, following the Keep a Changelog format. It checks whether changes affect behavior, configuration, tool names, or require a migration note.

Use it to prepare release notes from the current branch or a specified Git range without committing the result.

It reduces the chance of missing user-visible changes or incorrectly describing a breaking change before a 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/changelog/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/changelog/github.svg)](https://agentmods.dev/skills/solaceproducts/solace-broker-mcp/changelog)

Your own site

<a href="https://agentmods.dev/skills/solaceproducts/solace-broker-mcp/changelog"><img src="https://agentmods.dev/badge/skills/solaceproducts/solace-broker-mcp/changelog/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/changelog"><img src="https://agentmods.dev/badge/skills/solaceproducts/solace-broker-mcp/changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 2,332 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.

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.00042	$0.02332
Opus 5.5	$0.00017	$0.00933
Sonnet 5.5	$0.00008	$0.00466
Haiku 4.5	$0.00004	$0.00233

Measured 1mo ago against content hash 51d253b5e6c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

changelog 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 1mo 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/changelog/SKILL.md · 179 lines

How it starts

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

Changelog

Draft the [Unreleased] entry for the change on the current branch, matching the existing voice of CHANGELOG.md. Invoked with /changelog.

The skill drafts and prints a diff; it never commits. A human reviews the entry in the PR like any other change.

When to use

Before opening or updating a PR that changes behavior, config schema, or a tool.
Not needed for changes with no user-visible or operator-visible surface (pure test/refactor/docs) — those may carry a no-changelog label instead.

Usage

/changelog — draft an entry for the current branch's changes
/changelog <git-range> — draft for an explicit range, e.g. v0.5.0..HEAD or a single ticket's commits (required when drafting from main, which has no branch diff)

Steps

Step 1: Determine the change set and gather tickets

On a feature branch: git diff main...HEAD for the file changes and git log main..HEAD --format=%s%n%b for commit subjects/bodies — the commits are the primary source of the SOL ticket(s) and the "why."
With an explicit range argument: use it verbatim for both the diff and the log.
If HEAD is on the default branch (main) and no range was given: stop and ask for a range — do not diff main...HEAD (it is empty and would silently no-op).
PR context is optional: gh pr view --json title,body (or gh pr list --search <SOL-ticket> for a range) adds the "why." If gh is missing, unauthenticated, or the branch has no PR, continue from git data alone.
Ticket sourcing: take SOL-XXXXX from the branch name, commit subjects, or PR title. If none can be found, write Tracked under SOL-????. and flag it for the human — never invent a ticket number.

Step 2: Learn the house voice

Reference: docs/internal/changelog-style.md is the source of truth for style, length, and content rules. Read it before drafting.

For structural examples, read CHANGELOG.md: the [Unreleased] section for what is pending, and [0.5.0] and [0.3.0] for the structure of a breaking-change entry and the form of a migration table. Take structure from them, not length.

Read the full file on GitHub · 179 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.

1mo ago Changed · +23 lines 51d253b5e6c1
1mo ago Changed · +30 lines a08386e39c3c
2mo ago First seen · 126 lines · 42 tokens per session scan A 6a85cda9bc6b

Subscribe to this mod's changes

changelog is a skill published in the GitHub repository SolaceProducts/solace-broker-mcp (18 stars, last pushed yesterday), licensed Apache-2.0. It adds 42 tokens to every session and 2,332 once invoked, about $0.0002 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

changelog next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
changelogSolaceProducts/solace-broker-mcp	Skill	18	yesterday	Apache-2.0	A	42	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