A release command that prepares and publishes a semantic version, such as 1.2.0, for a software project. It updates the version and changelog, creates a Git tag, pushes it, and creates a GitHub Release.

Use it to release a specified version, derive one from a completed GitHub milestone, or choose from completed milestones. It handles version updates, changelog changes, tagging, pushing, and GitHub Release creation.

It removes the need to perform the release steps manually and helps keep the version, changelog, tag, and GitHub release aligned.

How CarlosDanielDev/maestro configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to CarlosDanielDev/maestro. 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/CarlosDanielDev/maestro/main/.claude/commands/release.md

Clone the repo

git clone --depth 1 https://github.com/CarlosDanielDev/maestro

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/commands/carlosdanieldev/maestro/release/github.svg)](https://agentmods.dev/commands/carlosdanieldev/maestro/release)

Your own site

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

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,325 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.00000	$0.02325
Opus 5.5	$0.00000	$0.00930
Sonnet 5.5	$0.00000	$0.00465
Haiku 4.5	$0.00000	$0.00232

Measured 1mo ago against content hash f8017bf929f6, 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.

.claude/commands/release.md · 217 lines

How it starts

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

Release

Create a semantic version release — bump version, update changelog, tag, push, and create GitHub Release.

Usage: /release or /release v0.4.0 or /release --milestone "v0.4.0"

Arguments

$ARGUMENTS may contain:

A version string (e.g., v0.4.0, 0.4.0) — use it directly
--milestone <name> — derive version from milestone name
Nothing — auto-detect from the active milestone with the most recently closed issues

Instructions

Execute ALL steps in order.

Step 1: Determine the Version

If a version was provided: use it (strip leading v if needed for Cargo.toml, keep v prefix for git tag).

If --milestone was provided: use the milestone name as the version (e.g., milestone "v0.4.0" → version 0.4.0).

If nothing provided:

Run gh api repos/{owner}/{repo}/milestones --jq '.[] | select(.open_issues == 0 and .closed_issues > 0) | .title' to find fully-completed milestones
If none found, run gh api repos/{owner}/{repo}/milestones --jq '.[] | .title + " (" + (.closed_issues|tostring) + "/" + ((.open_issues + .closed_issues)|tostring) + " closed)"' and ask the user to pick
Extract version from milestone title

Step 2: Validate Preconditions

Must be on main branch — if not, ask user to switch
Working tree must be clean — if dirty, ask to commit or stash
Tag must not already exist — run git tag -l v<version> to check
Run cargo test to ensure all tests pass
Run cargo clippy -- -D warnings -A dead_code to ensure no lint errors
Run cargo fmt -- --check to ensure formatting is clean

If any check fails, STOP and report the issue.

Note: These pre-bump tests confirm main is green. The post-bump tests in Step 4b are the ones that catch changelog-driven snapshot drift.

Step 3: Gather Changelog Content

Get the current version from Cargo.toml: grep '^version' Cargo.toml
Fetch all closed issues in the milestone: gh issue list --milestone "<milestone>" --state closed --json number,title,labels
Group issues by type using labels:
- feat: — issues with labels: enhancement, feature, type:feature
- fix: — issues with labels: bug, type:bug
- refactor: — issues with labels: refactor, type:refactor
- docs: — issues with labels: documentation, type:docs
- ci: — issues with labels: ci, type:ci
- perf: — issues with labels: performance, type:perf
- test: — issues with labels: test, type:test
- chore: — anything else
Format as a changelog section:

Read the full file on GitHub · 217 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 · 217 lines · 0 tokens per session scan A f8017bf929f6

Subscribe to this mod's changes

release is a command published in the GitHub repository CarlosDanielDev/maestro (31 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,325 tokens. 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-10-02.

Git and workflow Releases

release next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
releaseCarlosDanielDev/maestro	Command	31	20d ago	MIT	A	0	Claude Code
landgmickel/flow-next	Command	717	yesterday	MIT	A	13	Claude Code
qualityDesko77/claude-code-skills-1c	Command	90	yesterday	MIT	A	18	Claude Code
release-notesOpenHands/extensions	Command	176	yesterday	MIT	A	44	Claude Code
release-managerruvnet/agentic-flow	Command	838	today	none	A	0	Claude Code
create-prdsswift/ion	Command	5	yesterday	MIT	A	28	Claude Code
rally-merge-prddgonzal3/rally	Command	6	3d ago	MIT	A	0	Claude Code

maestro: Command for Claude Code