tempest: Skill for Claude Code

.claude/skills/release/SKILL.md

release is a skill for Claude Code from MattFlower/tempest. It costs 58 tokens per session (825 once invoked), scanned A, original, MIT.

A release workflow for the Tempest app that prepares a version from its changelog, updates project files, and creates a Git tag and GitHub release.

In plain words
What is it for?
Use it when you want to cut or tag a Tempest release. It reviews unreleased changes, suggests a semantic version, asks for confirmation, updates files, pushes the tag, and checks the GitHub release.
Why use it?
It removes the need to remember each release step and helps keep the changelog, app version, tag, and GitHub release aligned.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

This is MattFlower/tempest's own configuration. It tells Claude Code how to work on tempest itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tempest configures →

Reuse

Borrowing it

Nothing to install: this file belongs to MattFlower/tempest. 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/MattFlower/tempest/main/.claude/skills/release/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/MattFlower/tempest

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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/skills/mattflower/tempest/release/github.svg)](https://agentmods.dev/skills/mattflower/tempest/release)
Your own site
<a href="https://agentmods.dev/skills/mattflower/tempest/release"><img src="https://agentmods.dev/badge/skills/mattflower/tempest/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.

agentmods 80×15 button for release

Your own site · 80×15
<a href="https://agentmods.dev/skills/mattflower/tempest/release"><img src="https://agentmods.dev/badge/skills/mattflower/tempest/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 58 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 825 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00058 $0.00825
Opus 5.5 $0.00023 $0.00330
Sonnet 5.5 $0.00012 $0.00165
Haiku 4.5 $0.00006 $0.00082

Measured 1mo ago against content hash 4cc986e82f23, 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 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/release/SKILL.md · 104 lines

How it starts

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

Release Skill

Cut a new release for Tempest. Follow these steps exactly.

Step 1: Determine the version

  1. Read CHANGELOG.md and review the items under the ## Unreleased section.
  2. If the Unreleased section has no meaningful entries (only empty headings), stop and tell the user there is nothing to release.
  3. Based on the scope of changes, suggest a version number following semver. Show the user the summary and your suggested version.
  4. Ask the user to confirm or provide a different version number. Do not proceed until confirmed.

Step 2: Determine today's date

Run date +%Y-%m-%d to get today's date. Do not guess or hardcode the date.

Step 3: Update CHANGELOG.md

  1. Replace ## Unreleased with ## [VERSION] - YYYY-MM-DD (using the confirmed version and today's date).
  2. Immediately after the new version heading and its content, add a fresh Unreleased section with empty subsections:
## Unreleased

### Added

### Fixed

### Changed

### Removed
  1. Verify the edit looks correct by reading the first 25 lines of CHANGELOG.md.

Step 4: Update the app version

Update the version number in both places it appears:

  1. electrobun.config.ts — change the version field in the app object to the new VERSION.
  2. src/bun/pty-manager.ts — change the TERM_PROGRAM_VERSION value to the new VERSION.

Use the Edit tool for both changes.

Step 5: Detect VCS and commit

  1. Check whether the repo uses jujutsu or git:

    • If .jj directory exists: use jj commands
    • Else if .git directory exists: use git commands
    • NEVER use git commands for commits, bookmarks, or branches in a jj repo.
  2. For jujutsu repos:

    jj describe -m "Release VERSION"
    jj new
    jj bookmark set main -r @-
    jj git push
    
  3. For git repos:

    git add CHANGELOG.md
    git commit -m "Release VERSION"
    git push
    

Step 6: Tag the release

  1. For jujutsu repos:
    jj tag set vVERSION -r main
    
    Then push the tag via git (jj has no tag push support):
    git push origin vVERSION
    

Read the full file on GitHub · 104 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. 1mo ago First seen · 104 lines · 58 tokens per session scan A 4cc986e82f23

Subscribe to this mod's changes

release is a skill published in the GitHub repository MattFlower/tempest (8 stars, last pushed 7d ago), licensed MIT. It adds 58 tokens to every session and 825 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.

Related

Other skills, from other repositories

git-workflow

A Git workflow guide for organizing commits, branches, pull requests, releases, and automated version-control tasks. Git is the system developers use to track code changes and collaborate.

huangwb8/skills · 47 tokens

git-publish-release

A release assistant for GitHub, a service for hosting software projects. It compares project history and creates a GitHub Release with notes for a chosen version tag.

huangwb8/skills · 42 tokens

releasing-code

Prepare, publish, or repair a software release and write its release notes. Use for cutting a versioned release or editing release notes. NOT for updating an installed package, publishing articles, or discussing a release; for general documentation use documenting-code.

alexei-led/cc-thingz · 53 tokens

versioning-by-impact

Use when completing a task and deciding whether repository changes require a semantic version bump and changelog entry before commit/push.

rexleimo/aios · 29 tokens

release

Release a new version of pi-extensions: bump individual package versions (independent mode), update CHANGELOGs and READMEs, create per-package git tags, publish a GitHub release, and publish packages to npm via pnpm release. Use when the user asks to "cut a release", "release vX.Y.Z", "publish a new version", "create…

emanuelcasco/pi-mono-extensions · 86 tokens

Rig Release

Assess release readiness with a version baseline from HEAD, full gates, packaged file verification, and read-only release-note, migration, and contributor-reply drafts.

Borda/AI-Rig · 34 tokens