What is solo-release-notes?

A release-note writing workflow for GitHub releases. It reviews the changes between two release versions and turns them into notes that are easier for users to understand.

Use it after a GitHub release is published to write an overview, explain breaking changes, and provide upgrade notes.

Automatically generated commit lists can include internal fixes, miss important breaking changes, and be hard to read. This workflow separates user-facing changes from the raw changelog.

How hiero-ledger/solo configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to hiero-ledger/solo. 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/hiero-ledger/solo/main/.claude/skills/solo-release-notes/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/hiero-ledger/solo

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/hiero-ledger/solo/solo-release-notes/github.svg)](https://agentmods.dev/skills/hiero-ledger/solo/solo-release-notes)

Your own site

<a href="https://agentmods.dev/skills/hiero-ledger/solo/solo-release-notes"><img src="https://agentmods.dev/badge/skills/hiero-ledger/solo/solo-release-notes/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/hiero-ledger/solo/solo-release-notes"><img src="https://agentmods.dev/badge/skills/hiero-ledger/solo/solo-release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,377 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.00146	$0.03377
Opus 5.5	$0.00058	$0.01351
Sonnet 5.5	$0.00029	$0.00675
Haiku 4.5	$0.00015	$0.00338

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

Security

Grade A, and why

solo-release-notes 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 3d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (release-notes.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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/solo-release-notes/SKILL.md · 240 lines

How it starts

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

Solo Release Notes

semantic-release publishes every Solo GitHub release with an auto-generated list of feat:/fix: commit subjects. That list is complete but unreadable for users: CI and test fixes sit next to user-facing ones, reverted features still appear, and breaking changes that were not marked ! are invisible. This skill writes a curated summary for Solo users and places it above the untouched auto-generated changelog.

Run from the solo/ repo root (verify with git rev-parse --show-toplevel). The helper script lives next to this file: .claude/skills/solo-release-notes/release-notes.sh.

When to use

After the release workflow (flow-deploy-release-artifact.yaml) has published a release — the GitHub release for the tag must already exist.
To re-generate or refresh the summary of an existing release (the script strips the previous summary first).

Do not use for: preparing the release PR / README table (solo-prepare-release), smoke-testing a release candidate (solo-test-release), or tagging/publishing (that is the workflow).

Step 1 — Gather

SKILL_DIR=.claude/skills/solo-release-notes
bash "${SKILL_DIR}/release-notes.sh" gather <tag|latest> --out "<scratchpad>/release-notes-<tag>"

<tag> defaults to what the user named; use latest if they did not name one.
The previous tag is the nearest tag reachable from <tag>^ (correct for both main and release/N.N maintenance lines). Pass --previous <tag> only if the user asks for a different range.
Output directory contents:

File	Content
`changelog.md`	Current release body (semantic-release changelog), with any earlier generated summary removed
`commits.tsv`	`sha <TAB> PR number <TAB> subject` for every commit in range (release bot commit excluded)
`declared-breaking.tsv`	Commits with `type!:` or a `BREAKING CHANGE` footer
`prs.json`	Per PR: title, labels, files, author, `noBreakingChangesChecked`, `touchesProductCode`, description (PR template boilerplate removed)
`signals.md`	Filtered diffs of `version.ts`, `package.json`, flag names/defaults, command definitions, new schema migrations, removed command files, `env.md` entries

Read the full file on GitHub · 240 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

release-notes.sh 10.0 KB runs code

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.

3d ago First seen · 240 lines · 146 tokens per session scan A b37ecb9bd13a

Subscribe to this mod's changes

solo-release-notes is a skill published in the GitHub repository hiero-ledger/solo (45 stars, last pushed yesterday), licensed Apache-2.0. It adds 146 tokens to every session and 3,377 once invoked, about $0.0006 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-11-03.

Git and workflow Releases hacktoberfest

solo-release-notes next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
solo-release-noteshiero-ledger/solo	Skill	45	yesterday	Apache-2.0	A	146	Claude Code
update-changelogAzure/azure-sdk-for-net	Skill	6.1k	today	MIT	A	25	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
updater_guidesiddsachar/row-bot	Skill	1.7k	today	Apache-2.0	A	22	Claude Code, Codex

solo: Skill for Claude Code