A release procedure for a software project: it finds the previous version, reviews commits, increments the package version, creates a tag, pushes the changes, waits for the build, and publishes release notes.

Use it to prepare a new project release, summarize user-facing changes by category, monitor GitHub Actions, and publish the resulting draft release.

It turns several release steps into one documented sequence and helps keep the version, repository, build, and release page aligned.

How doctly/switchboard configures Claude Code

Reuse

Borrowing it

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

Clone the repo

git clone --depth 1 https://github.com/doctly/switchboard

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

Your own site

<a href="https://agentmods.dev/commands/doctly/switchboard/release"><img src="https://agentmods.dev/badge/commands/doctly/switchboard/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/doctly/switchboard/release"><img src="https://agentmods.dev/badge/commands/doctly/switchboard/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 778 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.00778
Opus 5.5	$0.00000	$0.00311
Sonnet 5.5	$0.00000	$0.00156
Haiku 4.5	$0.00000	$0.00078

Measured 1mo ago against content hash f6ab953f3294, 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 · 68 lines

How it starts

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

Perform a release for this project.

The command has two stops where you hand control back to the user: an uncommitted-changes check at the start, and release-note approval before publishing. Never publish without the second confirmation.

Step 1 — Check for uncommitted changes (stop point)

Run git status --porcelain and git diff --stat HEAD.

If anything is uncommitted or untracked: stop. Show the user the list of changed and untracked files with a one-line description of what each change is. Ask what they want to do with them (commit as part of the release, commit separately, stash, discard, leave alone). Do nothing else until they answer.
If the tree is clean: continue straight to Step 2 without asking anything.

Step 2 — Prepare the release (no stops)

Find the most recent version tag with git describe --tags --abbrev=0 and collect all commits between it and HEAD using git log {prev_tag}..HEAD --format="%B---"
Bump the version with npm version patch --no-git-tag-version
Commit the version bump with message: v{version}: {short summary of changes}
Create a git tag v{version}
Push commits and tag: git push && git push --tags
Wait for the GitHub Actions build to complete using gh run watch on the latest run
Confirm the build produced a draft release (gh release view v{version}). Do not publish it.

Step 3 — Show release notes for approval (stop point)

Write the release notes and print them in full in the chat. Then stop and wait.

End the turn with the notes and a single line asking the user to confirm before publishing. Do not run gh release edit, do not pass --draft=false, and do not take any further action in that turn.

Step 4 — Publish (only after the user confirms)

When the user says to go ahead, publish with the approved notes:

gh release edit v{version} --draft=false --notes "..."

If the user asks for edits to the notes first, revise and show them again, then wait for confirmation again.

Read the full file on GitHub · 68 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 · +30 lines f6ab953f3294
2mo ago First seen · 38 lines · 0 tokens per session scan A fc8c738d134a

Subscribe to this mod's changes

release is a command published in the GitHub repository doctly/switchboard (356 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 778 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-08-30.

Git and workflow Releases

release next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
releasedoctly/switchboard	Command	356	3d 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

switchboard: Command for Claude Code