A release command for the whetstone plugin that handles version updates, commits, pushes, mirroring, and local plugin updates. Versioning records which release of the plugin is installed.

Reviewing changes since the previous release, choosing a major, minor, or patch version increase, updating the changelog, and publishing the release.

It gathers changes and performs the release steps in one workflow, reducing the chance of forgetting version or changelog work.

release — Command for Claude Code by iliaal/whetstone

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.

Clone the repo

git clone --depth 1 https://github.com/iliaal/whetstone

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

Your own site

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

Per session 20 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,663 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.00020	$0.02663
Opus 5.5	$0.00008	$0.01065
Sonnet 5.5	$0.00004	$0.00533
Haiku 4.5	$0.00002	$0.00266

Measured 6d ago against content hash bc05a3db651c, 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 6d 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 · 98 lines

How it starts

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

Release

Run the full release pipeline for the whetstone plugin. This command owns all version ceremony — per-change edits do NOT bump versions or touch CHANGELOG.md. Those steps happen here, once, summarizing everything that accumulated since the last release.

Phase 1: Survey what changed since the last release

Confirm both repos are releasable before editing anything: whetstone and ~/ai/ai-skills must each have master checked out and contain origin/master, and ~/ai/ai-skills must have a clean working tree. release.sh aborts on any of these, so a bump applied on a feature branch has to be redone on master.
Find the current version in plugins/whetstone/.claude-plugin/plugin.json.
Run git log v<current-version>..HEAD --oneline (fallback: git log --since="<last release date>" --oneline) to list commits since the last tag.
Run git diff v<current-version>..HEAD --stat to see which files changed.
Classify the changes into added/changed/fixed/removed buckets per Keep a Changelog. Scan specifically for:
- New files under plugins/whetstone/{skills,agents,commands}/ → Added
- Deletions under the same paths → Removed
- Edits to existing components → Changed
- Commits with fix: prefix or bug-fix language → Fixed

Phase 2: Decide the semver bump

MAJOR if any breaking change (component removed, renamed, frontmatter contract changed)
MINOR if any new skill, agent, or command was added
PATCH otherwise (edits, doc updates, trigger-pattern tweaks)

Ask the user to confirm the bump type before writing anything, and offer a short rationale.

Phase 3: Apply the bump

Update version in plugins/whetstone/.claude-plugin/plugin.json, plugins/whetstone/.codex-plugin/plugin.json, and .claude-plugin/marketplace.json. All three must match.
Prepend a new CHANGELOG.md entry with today's date, the new version, a one-line summary, and buckets of commits grouped under ### Added / ### Changed / ### Fixed / ### Removed. Use the writing skill to polish the tone before committing. Name the skill in every skill-related bullet (ia-foo, foo-bar, or "foo bar" form) so the ai-skills CHANGELOG filter in release.sh picks it up; bullets that name only a command or agent are correctly excluded from ai-skills.
Run bash scripts/update-metadata.sh to sync component counts into plugin.json and marketplace.json descriptions.
Verify README.md agent/command/skill counts and tables still match reality — update if drift.
Validate JSON: jq . .claude-plugin/marketplace.json .agents/plugins/marketplace.json plugins/whetstone/.claude-plugin/plugin.json plugins/whetstone/.codex-plugin/plugin.json plugins/whetstone/.mcp.json.

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

6d ago Changed · +3 lines bc05a3db651c
1mo ago Changed dbfe3c479c9a
1mo ago First seen · 95 lines · 20 tokens per session scan A 7909907cb58a

Subscribe to this mod's changes

release is a command published in the GitHub repository iliaal/whetstone (35 stars, last pushed 2d ago), licensed MIT. It adds 20 tokens to every session and 2,663 once invoked, about $0.0001 per session on Opus 5.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.

Claude Code Code review Git and workflow Releases agent-skills ai-agents ai-tools claude-code-plugin

release

Release manager for frontend and mobile. Writes App Store notes, user-facing changelog, flags stale docs and landing copy. Actions: notes | changelog | docs | sync.

avelikiy/great_cto · 34 tokens

release-kick

A release command for the River Review project that checks release instructions and pull-request state, updates an out-of-date branch, and verifies the release after merging.

s977043/river-review · 64 tokens

release

Generate changelog, bump version, and create git tag.

Joncik91/ucai · 11 tokens

ship

Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…

PrabhdeepSingh/claude-plugins · 86 tokens

cancel-ship

Cancel active ship pipeline.

Joncik91/ucai · 4 tokens

open-pr

Create a pull request for the current branch following the the team's standard PR template.

carloshpdoc/ios-workflow-claude · 0 tokens

release

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Release

Phase 1: Survey what changed since the last release

Phase 2: Decide the semver bump

Phase 3: Apply the bump

What this file has done since we first saw it

Other commands, from other repositories

release

release-kick

release

ship

cancel-ship

open-pr