release-cut

release-cut is a skill for Claude Code, Codex from zakelfassi/skills-driven-development. It costs 70 tokens per session (955 once invoked), scanned A, original, MIT.

A release procedure for shipctl that updates its version, creates changelog entries from conventional commits, makes a Git tag, and drafts a GitHub release with compiled binaries.

In plain words
What is it for?
Use it to prepare stable releases or release candidates, including releases with cross-compiled platform binaries.
Why use it?
It groups the checks and publishing steps needed for a versioned release. It also stops before tagging if the working tree or tests are not ready.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Codex.

Good fit Use it to prepare stable releases or release candidates, including releases with cross-compiled platform binaries.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/zakelfassi/skills-driven-development/release-cut
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.

Any agent
npx skills add zakelfassi/skills-driven-development --skill release-cut
Clone the repo
git clone --depth 1 https://github.com/zakelfassi/skills-driven-development

Made for: Claude Code, Codex.

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-cut

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/zakelfassi/skills-driven-development/release-cut"><img src="https://agentmods.dev/badge/skills/zakelfassi/skills-driven-development/release-cut.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 955 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.00955
Opus 5.5 $0.00028 $0.00382
Sonnet 5.5 $0.00014 $0.00191
Haiku 4.5 $0.00007 $0.00096

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

Security

Grade A, and why

release-cut 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.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/release-cut.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

examples/cli-tool/skills/release-cut/SKILL.md · 100 lines

How it starts

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

Release Cut

Bump the version, generate a changelog, tag, and publish a GitHub release for shipctl.

Inputs

  • Target version (semver, e.g. 1.2.0 or patch/minor/major)
  • Release channel (defaults to stable; pre for release candidates)
  • Skip binary attach? (boolean, defaults to false)

Steps

  1. Verify the working tree is clean

    git status --porcelain
    

    If dirty, commit or stash before proceeding.

  2. Run the full test suite

    cargo test --workspace
    

    Abort if any test fails.

  3. Run the breaking-change audit (invoke the breaking-change-audit skill) Confirms no accidental public-interface regressions before tagging.

  4. Bump the version

    # For Rust:
    cargo set-version {version}   # or edit Cargo.toml manually
    # For Go:
    # Update version constant in cmd/root.go
    

    Commit the version bump:

    git commit -am "chore(release): bump version to {version}"
    
  5. Generate the changelog

    scripts/release-cut.sh --changelog-only {version}
    

    Review CHANGELOG.md — edit entries if the generated text is unclear. Commit: git commit -am "docs(changelog): {version} release notes"

  6. Create and push the tag

    git tag -a "v{version}" -m "Release v{version}"
    git push origin "v{version}"
    
  7. Trigger cross-compile and attach binaries The CI matrix builds all registered target triples (see cross-compile-matrix skill). Wait for the release workflow to complete:

    gh run watch --exit-status
    
  8. Draft the GitHub release

    gh release create "v{version}" \
      --title "v{version}" \
      --notes-file CHANGELOG.md \
      --draft
    

    Review the draft, then publish:

    gh release edit "v{version}" --draft=false
    
  9. Announce (if applicable) Post in the team channel: title, key changes, install command:

    cargo install shipctl --version {version}
    

Read the full file on GitHub · 100 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 100 lines · 70 tokens per session scan A 791d307e3845

Subscribe to this mod's changes

release-cut is a skill published in the GitHub repository zakelfassi/skills-driven-development (18 stars, last pushed 3mo ago), licensed MIT. It adds 70 tokens to every session and 955 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…

addyosmani/agent-skills · 89 tokens

comet-archive

A workflow for the fifth stage of Comet Classic: archiving a completed change, merging its specification updates, and finishing the branch. It uses Comet commands and a fixed layout for tracking the change.

rpamis/comet · 34 tokens

finishing-a-development-branch

A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.

jnMetaCode/superpowers-zh · 25 tokens

skillshare-changelog

Generate CHANGELOG.md entry from recent commits in conventional format. Also syncs the website changelog page. Use this skill whenever the user asks to: generate a changelog, document what changed between tags, or create a new CHANGELOG entry. If you see requests like "write the changelog for v0.17", "what changed…

runkids/skillshare · 134 tokens

skillshare-release

Prepare and review skillshare releases using the Release Please PR, verify the proposed version and changelog, inspect draft assets, and publish through the manual Publish Release workflow when explicitly authorized. Use when the user says "release", "prepare release", "cut a release", or asks to publish a new…

runkids/skillshare · 77 tokens

prepare-release

Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run /prepare-release.

CherryHQ/cherry-studio · 44 tokens