A release command that calculates the next version from recent Git commits and publishes it on GitHub.

Use it to run linting and tests, require a clean main branch, tag a new version, push it, and create release notes.

It removes the manual work of choosing a version, checking the project, creating Git tags, and writing the GitHub release.

How Sealjay/mcp-whatsapp configures Claude Code

Reuse

Borrowing it

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

Clone the repo

git clone --depth 1 https://github.com/Sealjay/mcp-whatsapp

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

Your own site

<a href="https://agentmods.dev/commands/sealjay/mcp-whatsapp/release"><img src="https://agentmods.dev/badge/commands/sealjay/mcp-whatsapp/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/sealjay/mcp-whatsapp/release"><img src="https://agentmods.dev/badge/commands/sealjay/mcp-whatsapp/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 328 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.00328
Opus 5.5	$0.00000	$0.00131
Sonnet 5.5	$0.00000	$0.00066
Haiku 4.5	$0.00000	$0.00033

Measured 2mo ago against content hash 8cef1f08f767, 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 2mo 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 · 29 lines

What it actually says

Release a new version. Determines the bump type from recent commits, runs the full checklist, tags, pushes, and creates a GitHub release.

Steps

Determine bump type from commits since the last tag:
- If $ARGUMENTS is major, minor, or patch, use that directly.
- Otherwise, inspect git log $(git describe --tags --abbrev=0)..HEAD --oneline:
  - Any commit mentioning "breaking" or "BREAKING CHANGE" -> major
  - Any commit with feat: prefix or new tool registrations -> minor
  - Otherwise -> patch
Calculate next version: parse the latest tag (git describe --tags --abbrev=0), increment the appropriate component, reset lower components to 0.
Pre-flight checks (abort on failure):
- git status must show a clean working tree (no uncommitted changes)
- git branch --show-current must be main
- make lint must pass
- make test must pass
Tag and release:
- git tag v<MAJOR>.<MINOR>.<PATCH>
- git push origin main
- git push origin v<MAJOR>.<MINOR>.<PATCH>
- gh release create v<MAJOR>.<MINOR>.<PATCH> --generate-notes
Report: print the new version, release URL, and a one-line summary.

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.

2mo ago First seen · 29 lines · 0 tokens per session scan A 8cef1f08f767

Subscribe to this mod's changes

release is a command published in the GitHub repository Sealjay/mcp-whatsapp (18 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 328 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 Go LLM Releases claude go mcp whatsapp

release next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
releaseSealjay/mcp-whatsapp	Command	18	20d ago	MIT	A	0	Claude Code
releaseexistential-birds/beagle	Command	85	1mo ago	Apache-2.0	A	12	Claude Code
releaseGoldziher/ai-rulez	Command	167	yesterday	MIT	A	4	Claude Code
shipGoldziher/ai-rulez	Command	167	yesterday	MIT	A	4	Claude Code
release-tagexistential-birds/beagle	Command	85	1mo ago	Apache-2.0	A	11	Claude Code
create-prdsswift/ion	Command	5	2d ago	MIT	A	28	Claude Code
rebase_promptfotoetienne/gru	Command	11	1mo ago	Apache-2.0	A	0	Claude Code

mcp-whatsapp: Command for Claude Code