What is release-prep?

A release checklist for AudioBash, an application that handles audio transcription. It updates version numbers, runs tests, builds supported platforms, and prepares changelog entries.

Use it when preparing an AudioBash release, including version bumps, test runs, platform builds, and changelog generation.

It gathers the main pre-release checks into one repeatable process, helping catch failures before a new version is published.

release-prep — Command by jamditis

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/jamditis/audiobash/release-prep

Clone the repo

git clone --depth 1 https://github.com/jamditis/audiobash

Made for: Claude Code.

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 1,889 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. 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.00000	$0.01889
Opus 5	$0.00000	$0.00945
Sonnet 5	$0.00000	$0.00378
Haiku 4.5	$0.00000	$0.00189

Measured 2d ago against content hash ffddf9e75992, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

release-prep scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf dist/

.claude/commands/release-prep.md · 296 lines

How it starts

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

Release Preparation

Prepare AudioBash for a new release by running all tests, building all platforms, updating version numbers, and generating changelog entries.

Your Role

You are the release manager preparing AudioBash for a new version release. Execute all pre-release checks systematically.

Release Checklist

1. Version Bump

Determine release type:

Major (x.0.0) - Breaking changes, major new features
Minor (1.x.0) - New features, no breaking changes
Patch (1.0.x) - Bug fixes only

Update version in all locations:

# Update package.json version
npm version [major|minor|patch] --no-git-tag-version

# Verify version updated
grep '"version"' package.json

Files that may need manual version updates:

package.json - npm version handles this
electron/main.cjs - Check for hardcoded version strings
README.md - Update version badges if present
docs/index.html - Update download links with new version

2. Run Test Suite

Execute the full test suite and verify all tests pass:

# Run all tests
npm test

# Check for test failures
echo "Exit code: $?"

Expected output:

All 70+ tests pass
No errors or warnings
100% of test suites pass

If tests fail:

Fix failing tests before proceeding
Do NOT release with failing tests
Re-run full suite after fixes

3. Build All Platforms

Build for all supported platforms:

# Clean previous builds
rm -rf dist/

# Build all platforms (sequential to avoid conflicts)
npm run electron:build:mac:arm64
npm run electron:build:mac:x64
npm run electron:build:win
npm run electron:build:linux

Verify artifacts created:

✓ dist/AudioBash-{version}-arm64.dmg (macOS ARM64)
✓ dist/AudioBash-{version}-x64.dmg (macOS x64)
✓ dist/AudioBash Setup {version}.exe (Windows)
✓ dist/AudioBash-{version}.AppImage (Linux)
✓ dist/AudioBash-{version}.deb (Linux)

Record artifact sizes:

ls -lh dist/*.dmg dist/*.exe dist/*.AppImage dist/*.deb

Read the full file on GitHub · 296 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 · 296 lines · 0 tokens per session scan C ffddf9e75992

Subscribe to this mod's changes

release-prep is a command published in the GitHub repository jamditis/audiobash (5 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,889 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Creative and media Git and workflow Testing ai audio bash claude-code cli commandline

release-prep