A coding command that prepares a software release by changing the package version, creating a Git tag, and pushing it so GitHub Actions can publish the package to npm.

It helps review changes since the previous release, choose a major, minor, or patch version, tag the release, push it, and trigger automated npm publishing.

It avoids manually deciding version changes and performing each release step. It uses commit messages to distinguish breaking changes, new features, and smaller fixes.

How gregpriday/create-image-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to gregpriday/create-image-mcp. 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/gregpriday/create-image-mcp/main/.claude/commands/release.md

Clone the repo

git clone --depth 1 https://github.com/gregpriday/create-image-mcp

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/gregpriday/create-image-mcp/release/github.svg)](https://agentmods.dev/commands/gregpriday/create-image-mcp/release)

Your own site

<a href="https://agentmods.dev/commands/gregpriday/create-image-mcp/release"><img src="https://agentmods.dev/badge/commands/gregpriday/create-image-mcp/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/gregpriday/create-image-mcp/release"><img src="https://agentmods.dev/badge/commands/gregpriday/create-image-mcp/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 950 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.00950
Opus 5.5	$0.00000	$0.00380
Sonnet 5.5	$0.00000	$0.00190
Haiku 4.5	$0.00000	$0.00095

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

How it starts

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

Release @gpriday/create-image-mcp

NPM publishing is handled by GitHub Actions on tag push. This command bumps the version, tags, and pushes.

Current State

Git status: !git status
Current branch: !git branch --show-current
Latest tag: !git describe --tags --abbrev=0 2>/dev/null || echo "none"
Current version: !node -p "require('./package.json').version"
Changes since last tag: !git log $(git describe --tags --abbrev=0 2>/dev/null || echo "HEAD")..HEAD --oneline 2>/dev/null || echo "No previous tags"

Steps

Step 1: Analyze Changes & Determine Version

Version bump override: $ARGUMENTS

If $ARGUMENTS is empty, auto-detect version bump:

Read all commits since the last git tag. Analyze commit messages following Conventional Commits:

MAJOR (breaking): Look for "BREAKING CHANGE:", "!" after type (e.g., "feat!:"), or "major:" prefix
MINOR (feature): Look for "feat:", "feature:", new functionality
PATCH (fix): Look for "fix:", "bugfix:", "chore:", "docs:", "refactor:", "test:", "style:", improvements

Rules:

If any BREAKING CHANGE found → MAJOR bump
If any feat/feature found (no breaking) → MINOR bump
Otherwise → PATCH bump
If no commits since last tag → Ask user if they want to proceed with PATCH

Calculate new version based on current package.json version and bump type.

Step 2: Pre-Release Validation

Check for Uncommitted Changes
- Run git status --porcelain
- If ANY uncommitted changes exist: STOP and tell user to commit or stash first
Verify Prerequisites
- Must be on main branch (STOP if not)
- Run npm test - all tests must pass (STOP if any fail)

Step 3: Update package.json and package-lock.json

npm version [NEW_VERSION] --no-git-tag-version

This updates the version in both package.json and package-lock.json, so the lockfile doesn't drift.

Also move the ## [Unreleased] heading in CHANGELOG.md to ## [NEW_VERSION] - YYYY-MM-DD (today's date) if it exists.

Read the full file on GitHub · 113 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 · +5 lines eaa2bd940c59
2mo ago First seen · 108 lines · 0 tokens per session scan A 4e14eacc2a41

Subscribe to this mod's changes

release is a command published in the GitHub repository gregpriday/create-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 950 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-31.

Git and workflow Releases

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

create-image-mcp: Command for Claude Code