release

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 CodeCodex

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 skills/mattflower/tempest/release
Any agent
npx skills add MattFlower/tempest --skill release
Clone the repo
git clone --depth 1 https://github.com/MattFlower/tempest

Made for: Claude Code, Codex.

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. 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.00058 $0.00825
Opus 5 $0.00029 $0.00413
Sonnet 5 $0.00012 $0.00165
Haiku 4.5 $0.00006 $0.00082

Measured 2d ago against content hash 4cc986e82f23, 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 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 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.

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. 2d 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 (7 stars, last pushed 25d ago), licensed MIT. It adds 58 tokens to every session and 825 once invoked, about $0.0003 per session on Opus 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

codex-autoresearch

Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…

leo-lilinxiao/codex-autoresearch · 80 tokens

map-wayfind

Decision-frontier wayfinding: build and work a durable map of open design decisions BEFORE planning, for large or foggy efforts where /map-plan would force premature decomposition. Use when a task is too big or too vague to decompose — many unknowns, tangled decisions, or "I'm not even sure what to build yet" — and…

azalio/map-framework · 182 tokens

map-fast

Minimal workflow for small, low-risk changes — no planning, no learning.

azalio/map-framework · 17 tokens

clipboard

Copy text to clipboard with optional rich formatting. Triggers on "copy to clipboard", "copy that", "pbcopy", "copy formatted", "copy rich text".

CodeAlive-AI/ai-driven-development · 36 tokens

neo4j-modeling-skill

Design, review, and refactor Neo4j graph data models. Use when choosing node labels vs relationship types vs properties, migrating relational/document schemas to graph, detecting anti-patterns (generic labels, supernodes, missing constraints), designing intermediate nodes for n-ary relationships, enforcing schema with…

neo4j-contrib/neo4j-skills · 152 tokens

alphafold-database

Access AlphaFold 200M+ AI-predicted protein structures. Retrieve structures by UniProt ID, download PDB/mmCIF files, analyze confidence metrics (pLDDT, PAE), for drug discovery and structural biology.

agent-skills-hub/agent-skills-hub · 54 tokens