An automated release command for the gsd-taskmanager app or its MCP server. It coordinates version changes, checks, Git operations, pull requests, tags, and a GitHub release.

Use it for patch, minor, major, or explicit version releases, including clean-branch checks, version bumps, type checks, linting, tests, commits, pushes, pull requests, merges, tags, and GitHub release creation.

It removes the need to repeat the full release sequence manually and stops when the branch, verification, review, or merge requirements are not satisfied.

release — Command by vscarpenter

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/vscarpenter/gsd-task-manager/release

Clone the repo

git clone --depth 1 https://github.com/vscarpenter/gsd-task-manager

Made for: Claude Code.

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

When invoked 607 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.

Model	Per session	Once invoked
Fable 5	$0.00039	$0.00607
Opus 5	$0.00019	$0.00303
Sonnet 5	$0.00008	$0.00121
Haiku 4.5	$0.00004	$0.00061

Measured 2d ago against content hash c015f9e55472, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 2d 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 · 42 lines

How it starts

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

/release

Release the gsd-taskmanager app or MCP server. Replaces the recurring "bump version to N, commit, push, PR, merge, tag, GH release" manual flow.

Inputs

$ARGUMENTS is either:

patch / minor / major — bump the matching SemVer segment of package.json (workspace root).
An explicit version like 9.4.0 — pin to that exact value.

Steps

Branch preflight — confirm working tree is clean (git status --porcelain). If dirty, ask whether to stash or include changes.
Branch creation — if on main, create chore/release-<version>. (The no-main-commits.sh hook will block otherwise.)
Version bump — update package.json and packages/mcp-server/package.json if the MCP server is part of the release. Use npm version --no-git-tag-version or edit directly.
Verification gate — run bun typecheck && bun lint && bun run test. Halt if any fail.
Commit — chore(release): vX.Y.Z with a body listing the user-visible changes since the previous tag (git log --oneline <prev-tag>..HEAD).
Push and PR — push the branch, open a PR titled Release vX.Y.Z with the changelog as the body.
Wait for review or self-merge — if the user has authority, ask whether to merge immediately.
Tag — after merge, git fetch origin main, git tag vX.Y.Z, git push origin vX.Y.Z.
GitHub release — gh release create vX.Y.Z --generate-notes --title "vX.Y.Z".
MCP publish (if applicable) — if the MCP server bumped, run npm publish from packages/mcp-server/ (requires npm login).

Anti-goals

Don't run on a dirty working tree without explicit user OK.
Don't push tags before the version-bump PR is merged.
Don't publish to npm without user confirmation — that step is hard to reverse.

Verification before declaring done

Version bump merged on main.
Tag exists on remote.
GitHub release page shows the new version.
If MCP server was published, npm view gsd-mcp-server version returns the new value.

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

2d ago First seen · 42 lines · 39 tokens per session scan A c015f9e55472

Subscribe to this mod's changes

release is a command published in the GitHub repository vscarpenter/gsd-task-manager (24 stars, last pushed 4d ago), licensed MIT. It adds 39 tokens to every session and 607 once invoked, about $0.0002 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-30.

Git and workflow Releases eisenhower-matrix mcp-server model-context-protocol nextjs npm-package task-manager

release

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

/release

Inputs

Steps

Anti-goals

Verification before declaring done

What this file has done since we first saw it

Other commands, from other repositories

make-pr

release

deploy-prod

release

changelog

release