release-prepare

release-prepare is a command for Claude Code from C0ntr0lledCha0s/claude-code-plugin-automations. It costs 14 tokens per session (1,221 once invoked), scanned A, original, MIT.

A release-preparation command that reviews Git commits since the last release, chooses a version change, and drafts release documentation. A release is a published version of a software project, and a changelog records what changed.

In plain words
What is it for?
Use it before publishing a patch, minor, or major release, or let it infer the change from commit types. It prepares grouped changelog entries and release notes from the repository history.
Why use it?
It removes the manual work of reconstructing what changed and deciding how the version should advance. It also shows which version files may need updating before publication.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the github-workflows plugin — 8 skills, 9 commands, 4 agents shipped together

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.

agentmods
npx agentmods add commands/c0ntr0lledcha0s/claude-code-plugin-automations/release-prepare
Clone the repo
git clone --depth 1 https://github.com/C0ntr0lledCha0s/claude-code-plugin-automations

Made for: Claude Code.

Or install github-workflows, the plugin that ships this one along with the rest of its 8 skills, 9 commands, 4 agents.

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.

agentmods badge for release-prepare

README.md
[![agentmods](https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/release-prepare.svg)](https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/release-prepare)
Your own site
<a href="https://agentmods.dev/commands/c0ntr0lledcha0s/claude-code-plugin-automations/release-prepare"><img src="https://agentmods.dev/badge/commands/c0ntr0lledcha0s/claude-code-plugin-automations/release-prepare.svg" alt="Measured on agentmods" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,221 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.01221
Opus 5 $0.00007 $0.00611
Sonnet 5 $0.00003 $0.00244
Haiku 4.5 $0.00001 $0.00122

Measured 6d ago against content hash 555ef39007d7, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

release-prepare 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 6d 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.

github-workflows/commands/release-prepare.md · 207 lines

How it starts

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

Prepare Release

Analyzes commits since the last release and prepares all release artifacts.

Usage

/release-prepare auto       # Auto-detect version from commits
/release-prepare minor      # Force minor version bump
/release-prepare major      # Force major version bump
/release-prepare patch      # Force patch version bump

What This Does

  1. Analyze Commits: Get all commits since last release tag
  2. Determine Version: Calculate version bump based on commit types
  3. Generate Changelog: Create changelog entries grouped by type
  4. Create Release Notes: Generate comprehensive release notes
  5. Prepare Files: Show what version files need updating

Workflow

Step 1: Get Last Release

Find the most recent release tag and analyze commits since then:

# Get last release tag
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")
echo "Last release: ${LAST_TAG:-'No previous release'}"

# Count commits since last release
if [ -n "$LAST_TAG" ]; then
  COMMIT_COUNT=$(git rev-list --count $LAST_TAG..HEAD)
else
  COMMIT_COUNT=$(git rev-list --count HEAD)
fi
echo "Commits since last release: $COMMIT_COUNT"

Step 2: Analyze Commit Types

Parse commits using conventional commit format:

# Get commits since last tag
if [ -n "$LAST_TAG" ]; then
  COMMITS=$(git log $LAST_TAG..HEAD --pretty=format:"%s")
else
  COMMITS=$(git log --pretty=format:"%s")
fi

# Count by type
FEAT_COUNT=$(echo "$COMMITS" | grep -c "^feat" || echo "0")
FIX_COUNT=$(echo "$COMMITS" | grep -c "^fix" || echo "0")
BREAKING_COUNT=$(echo "$COMMITS" | grep -c "!" || echo "0")
BREAKING_FOOTER=$(echo "$COMMITS" | grep -c "BREAKING CHANGE" || echo "0")

echo "Features: $FEAT_COUNT"
echo "Fixes: $FIX_COUNT"
echo "Breaking changes: $((BREAKING_COUNT + BREAKING_FOOTER))"

Step 3: Determine Version Bump

Based on argument or auto-detection:

Auto-detection logic:

  • Any breaking changes (! or BREAKING CHANGE) → MAJOR
  • Any features (feat:) → MINOR
  • Only fixes/docs/chores → PATCH

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

  1. 6d ago First seen · 207 lines · 14 tokens per session scan A 555ef39007d7

Subscribe to this mod's changes

release-prepare is a command published in the GitHub repository C0ntr0lledCha0s/claude-code-plugin-automations (3 stars, last pushed 6mo ago), licensed MIT. It adds 14 tokens to every session and 1,221 once invoked, about $0.0001 per session on Opus 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.