A release-preparation checklist for getting a software version ready to publish. It covers quality checks, documentation, versioning, changelog entries, security, dependencies, and validation.

Use it to inspect recent commits, choose or confirm a version, prepare a changelog, check builds and tests, update documentation, and validate the release.

It reduces the chance of releasing unfinished work, known serious bugs, undocumented breaking changes, or vulnerable dependencies.

release — Skill for Claude Code by ashtonian/llm-init

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add ashtonian/llm-init --skill release

Clone the repo

git clone --depth 1 https://github.com/ashtonian/llm-init

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/ashtonian/llm-init/release/github.svg)](https://agentmods.dev/skills/ashtonian/llm-init/release)

Your own site

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

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

When invoked 515 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.00010	$0.00515
Opus 5.5	$0.00004	$0.00206
Sonnet 5.5	$0.00002	$0.00103
Haiku 4.5	$0.00001	$0.00052

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

Security

Grade A, and why

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 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.

templates/.claude/skills/release/SKILL.md · 77 lines

How it starts

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

Prepare a release with checklist, changelog, and validation.

Instructions

Read docs/spec/.llm/PROGRESS.md for recent changes and known issues.
Read .claude/rules/agent-guide.md for quality gates.
Determine the version number (ask user if not specified).

Pre-Release Checklist

All quality gates pass (build, test, lint -- run from agent guide rules)
No known critical bugs
All planned features for this release are complete
Documentation is up to date (README, API docs, CHANGELOG)
Breaking changes are documented with migration instructions
Performance benchmarks pass (if applicable)
Security review completed (or run /security-review now)
Dependencies are up to date (no critical CVEs)

Changelog Generation

Review commits since the last tag (git log $(git describe --tags --abbrev=0)..HEAD --oneline) and categorize:

## [version] - {date}

### Added
- {new features}

### Changed
- {modifications to existing features}

### Fixed
- {bug fixes}

### Removed
- {removed features}

### Security
- {security fixes}

### Breaking Changes
- {breaking changes with migration instructions}

Release Validation

All tests pass on a clean checkout (git stash && tests && git stash pop)
Application starts successfully
Smoke tests pass (key user flows work)
No regressions in core functionality
Release artifacts build correctly (Docker images, binaries, packages)

Release Execution

Present the checklist and changelog to the user for approval. Once approved:

Create the tag: git tag -a v{version} -m "{changelog summary}"
If GoReleaser is configured: goreleaser release (or push the tag for CI)
If npm: npm publish (with appropriate flags)
Update PROGRESS.md with release note

Post-Release

Verify release artifacts are published
Verify container images are available (if applicable)
Update any deployment configurations
Notify stakeholders

Read the full file on GitHub · 77 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 First seen · 77 lines · 10 tokens per session scan A 8de91b08971a

Subscribe to this mod's changes

release is a skill published in the GitHub repository ashtonian/llm-init (2 stars, last pushed today), licensed MIT. It adds 10 tokens to every session and 515 once invoked, about $0.0000 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-31.

Git and workflow Releases

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

release