release

A release command that prepares a production version by merging the development branch into the main branch, updating the version number, and creating a GitHub release.

In plain words
What is it for?
Use it to validate a release, check CI and database migrations, run type and health checks, choose a major, minor, or patch version, and create the release.
Why use it?
It puts the checks, version choice, branch preparation, and release steps into one documented process before code is published.

Command for Claude Code

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/jayminwest/kotadb/release
Clone the repo
git clone --depth 1 https://github.com/jayminwest/kotadb

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 2,318 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.02318
Opus 5 $0.00000 $0.01159
Sonnet 5 $0.00000 $0.00464
Haiku 4.5 $0.00000 $0.00232

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

Security

Grade A, and why

release scanned grade A 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 3d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -f http://localhost:3000/health || exit 1
.claude/commands/release/release.md · 353 lines

How it starts

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

/release

Template Category: Action

Create a production release by merging developmain with automated versioning, validation, and GitHub release creation.

Pre-Release Validation

Before creating a release, the command performs comprehensive checks:

  1. Clean Working Tree: Ensure no uncommitted changes (git status --short must be empty)
  2. CI Status: Verify all GitHub Actions are passing on develop branch
  3. Migration Sync: Run bun run test:validate-migrations to check drift
  4. Type Checking: Execute bunx tsc --noEmit for type safety
  5. SQLite Schema Validation: Verify database schema is correct
  6. Health Checks: Verify API endpoints are responding correctly

Version Bumping

Prompt user for version bump type:

  • major: Breaking changes (1.0.0 → 2.0.0)
  • minor: New features, backward compatible (1.0.0 → 1.1.0)
  • patch: Bug fixes, backward compatible (1.0.0 → 1.0.1)

Updates:

  • app/package.json version field
  • Creates version bump commit: chore: bump version to X.Y.Z

Release Process

Step 1: Prepare Release Branch

git checkout develop
git pull --rebase origin develop
git checkout -b release/vX.Y.Z

Step 2: Update Version

cd app
# Update package.json version
bun run version <major|minor|patch>
# Commit version change
git add package.json
git commit -m "chore: bump version to X.Y.Z"

Step 3: Generate Changelog

Extract commits from develop since last release:

git log $(git describe --tags --abbrev=0)..HEAD --oneline --no-merges

Group by type:

  • Features: commits starting with feat:
  • Bug Fixes: commits starting with fix:
  • Chore: commits starting with chore:
  • Documentation: commits starting with docs:
  • Performance: commits starting with perf:
  • Refactor: commits starting with refactor:

Format as markdown for release notes.

Step 4: Create Release PR

git push -u origin release/vX.Y.Z
gh pr create \
  --base main \
  --head release/vX.Y.Z \
  --title "Release vX.Y.Z" \
  --body "$(cat <<'EOF'
## Release vX.Y.Z

### Summary
Brief description of release highlights

### Changelog
<Generated changelog from commits>

### Pre-Release Checklist
- [x] All CI checks passing on develop
- [x] Clean working tree verified
- [x] Migration sync validated
- [x] Type checking passed
- [x] SQLite schema validated
- [x] Health checks passed locally

### Deployment Plan
1. Merge this PR to main
2. Create GitHub release for distribution
3. Monitor logs for errors
4. Verify local health checks pass

### Rollback Plan
If issues arise:
1. Revert merge commit on main
2. Redeploy previous version
3. Create hotfix branch from main for urgent fixes

🤖 Generated with [Claude Code](https://claude.com/claude-code)
EOF
)"

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

  1. 3d ago First seen · 353 lines · 0 tokens per session scan A c6db35909581

Subscribe to this mod's changes

release is a command published in the GitHub repository jayminwest/kotadb (102 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,318 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.