What is prepare-release?

A command for preparing a software release before publication. It can choose a version from conventional commits, which are commit messages using standard prefixes such as feat and fix, and coordinates checks, scripts, and release notes.

Use it to infer or specify a release version, run pre-release checks, coordinate reviews, execute the preparation script, and create enhanced release notes.

It organizes pre-release validation and version selection so changes are reviewed and documented before publishing.

How erraggy/oastools configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to erraggy/oastools. 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/erraggy/oastools/main/.claude/skills/prepare-release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/erraggy/oastools

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/skills/erraggy/oastools/prepare-release/github.svg)](https://agentmods.dev/skills/erraggy/oastools/prepare-release)

Your own site

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

Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,249 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.00050	$0.02249
Opus 5.5	$0.00020	$0.00900
Sonnet 5.5	$0.00010	$0.00450
Haiku 4.5	$0.00005	$0.00225

Measured 1mo ago against content hash 26718ae58c3f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

prepare-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 1mo 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/skills/prepare-release/SKILL.md · 273 lines

How it starts

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

prepare-release

Prepare a new release by running comprehensive pre-release checks and updates.

Usage:

/prepare-release <version> - Use specified version (e.g., /prepare-release v1.46.0)
/prepare-release - Infer version from conventional commits

Version Inference

If no version is provided, analyze commits since the last tag:

Step 1: Get Commits Since Last Release

LAST_TAG=$(git describe --tags --abbrev=0)
echo "Last release: $LAST_TAG"
git log "$LAST_TAG"..HEAD --oneline

Step 2: Determine Version Bump

Parse conventional commit prefixes:

Any BREAKING CHANGE: footer or type with exclamation suffix (e.g., feat!:, fix!:) → MAJOR bump
Any feat: or feat(scope): → MINOR bump
Only fix:, chore:, docs:, refactor:, test:, perf: → PATCH bump

Step 3: Propose or Prompt

If clear signal: Propose the version with explanation:

Analyzing commits since v1.45.2...

Found 4 commits:
- feat(parser): add streaming support
- fix(validator): handle empty schemas
- chore: update dependencies
- docs: improve examples

Recommendation: **v1.46.0** (minor bump due to new feature)

Proceed with v1.46.0? [Yes / Different version]

If ambiguous: Prompt user to choose:

Analyzing commits since v1.45.2...

Found 3 commits with unclear versioning signal:
- refactor(core): reorganize internal structure
- perf: optimize memory usage
- chore: update dependencies

What version bump is appropriate?
- v1.45.3 (patch) - Bug fixes and minor improvements
- v1.46.0 (minor) - Notable improvements worth a minor bump
- Other - Specify a different version

Process

You are the DevOps Engineer coordinating a release. Execute the following phases:

Phase 1: Launch Background Agents

Launch these agents in background mode (run_in_background: true) to run concurrently:

DevOps Engineer - Pre-release validation:
- Check commits since last release tag
- Run make bench-quick for quick local regression check (~2 min)
- Create feature branch chore/<version>-release-prep

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

1mo ago First seen · 273 lines · 50 tokens per session scan A 26718ae58c3f

Subscribe to this mod's changes

prepare-release is a skill published in the GitHub repository erraggy/oastools (6 stars, last pushed 9d ago), licensed MIT. It adds 50 tokens to every session and 2,249 once invoked, about $0.0002 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-31.

Git and workflow Releases go openapi openapi-specification openapi3 openapi31 swagger

lathe-release

Run Lathe release validation and publishing workflows. Use when the user asks to prepare, validate, cut, tag, publish, or ship a Lathe versioned release; runs the captured pre-release regression gate before tagging.

lathe-cli/lathe · 48 tokens

conventional-git

Conventional Commits v1.0.0 branch naming and commit message standards for GitHub and GitLab projects. Use when creating branches, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases…

Harmeet10000/skills · 77 tokens

octocat

Handles git and GitHub operations using the gh CLI. Use when the user asks about pull requests (PRs), GitHub issues, repo management, branching, merging, rebasing, cherry-picking, merge conflict resolution, commit history cleanup, pre-commit hook debugging, GitHub Actions workflows, or releases. Covers creating and…

Harmeet10000/skills · 100 tokens

release

Fully automate a release with version-bump and childhood.

thedotmack/claude-mem · 13 tokens

release-notes

Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.

phuryn/pm-skills · 57 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

oastools: Skill for Claude Code