A release checklist for a Ruby gem, a reusable Ruby software package. It runs tests and style checks, updates release files, verifies the version, and prepares a pull request.

It helps check the code, fix style issues, regenerate the manifest, review changes since the last tag, update the changelog, manage dependencies, and create a release branch and pull request.

It reduces the chance of publishing a release with failing tests, incorrect versioning, missing changelog details, or an outdated package manifest.

How pusewicz/cf-mcp configures Claude Code

Reuse

Borrowing it

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

Clone the repo

git clone --depth 1 https://github.com/pusewicz/cf-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/pusewicz/cf-mcp/release-gem.svg)](https://agentmods.dev/commands/pusewicz/cf-mcp/release-gem)

Your own site

<a href="https://agentmods.dev/commands/pusewicz/cf-mcp/release-gem"><img src="https://agentmods.dev/badge/commands/pusewicz/cf-mcp/release-gem.svg" alt="Measured on agentmods" 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 342 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.1	$0.00000	$0.00342
Opus 5	$0.00000	$0.00171
Sonnet 5	$0.00000	$0.00068
Haiku 4.5	$0.00000	$0.00034

Measured 6d ago against content hash b60f2397d9c6, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

release-gem 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-gem.md · 27 lines

What it actually says

Prepare a release of the gem by running checks, ensuring version is bumped, changelog is updated, and creating a PR.

Run rake test to ensure all tests pass. If tests fail, stop and report the failures.
Run rake standard to check code style. If there are issues, run rake standard:fix and include the fixes.
Run rake manifest to regenerate Manifest.txt.
Check the current version in lib/cf/mcp/version.rb.
Check git log to see what changes have been made since the last release tag (use git describe --tags --abbrev=0 to find the last tag, then git log <tag>..HEAD --oneline).
If there are meaningful changes that warrant a release:
- If the version hasn't been bumped yet (no version bump commit since last tag), ask the user what type of version bump is needed (patch/minor/major) and bump accordingly.
- Update CHANGELOG.md with a new entry for the current version, documenting the changes since the last release.
- Add the comparison link at the bottom of CHANGELOG.md.
Run bundle install to update Gemfile.lock if version was changed.
Create a new branch named release/vX.Y.Z where X.Y.Z is the version number.
Commit all changes with message "Prepare release vX.Y.Z".
Push the branch and create a PR with:
- Title: "Release vX.Y.Z"
- Body: Include the changelog entry for this version and a checklist for release steps.

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 First seen · 27 lines · 0 tokens per session scan A b60f2397d9c6

Subscribe to this mod's changes

release-gem is a command published in the GitHub repository pusewicz/cf-mcp (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 342 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 Languages Releases Ruby ai-tools claude-code cute-framework model-context-protocol

cf-mcp: Command for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

rel

release

sdd-discover-standards

setup

aw-upgrade

write-rbs