A release process for publishing a new version of several related packages. A package is a separately versioned piece of software that can be published for others to install.

Use it to prepare a release branch, audit changesets, update package versions, open and approve the release pull request, trigger publishing, and verify the package, tag, and GitHub release.

It reduces release mistakes by checking included changes, version consistency, documentation, approvals, and the published results.

How thomas-powers-jr/cadence configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to thomas-powers-jr/cadence. 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/thomas-powers-jr/cadence/main/.claude/skills/release-cut/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/thomas-powers-jr/cadence

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/thomas-powers-jr/cadence/release-cut/github.svg)](https://agentmods.dev/skills/thomas-powers-jr/cadence/release-cut)

Your own site

<a href="https://agentmods.dev/skills/thomas-powers-jr/cadence/release-cut"><img src="https://agentmods.dev/badge/skills/thomas-powers-jr/cadence/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/thomas-powers-jr/cadence/release-cut"><img src="https://agentmods.dev/badge/skills/thomas-powers-jr/cadence/release-cut.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 1,656 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.00092	$0.01656
Opus 5.5	$0.00037	$0.00662
Sonnet 5.5	$0.00018	$0.00331
Haiku 4.5	$0.00009	$0.00166

Measured 27d ago against content hash f3fcaadb4744, 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 27d 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-cut/SKILL.md · 119 lines

How it starts

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

Release cut

Publishing is irreversible. Two hard consent gates in this flow: merging the release PR, and firing the Release workflow. Neither happens on a generic "continue" — restate the action and get an explicit go-ahead.

1 — Inventory what ships

git fetch origin --prune, then git log $(git describe --tags --abbrev=0)..origin/main --oneline --no-merges.
Map commits to phases; write the bundle list (this becomes the PR body and the CLAUDE.md version-line summary).
Audit changesets: every feature PR in the bundle should have left a .changeset/*.md. For any missing one (discipline has slipped before — five had to be reconstructed retroactively for v1.42.0), reconstruct it from the PR description now, and note the slip in the handoff.

2 — Version bump (lockstep)

On a release branch: pnpm changeset:version.
Verify all five published packages (core, types, host-claude-code, host-codex, host-toolkit) moved to the identical new version and testkit did not. Anything else is a stop-and-investigate.
Update the version line near the top of CLAUDE.md to the new version string. The doc-sync pre-commit hook aborts the commit otherwise, and packages/core/tests/docs/doc-sync-hook.test.ts re-asserts it in CI.
Add a matching ## [x.y.z] heading to CHANGELOG.md for the new version, in the same commit. The same doc-sync pre-commit hook now checks CHANGELOG.md too — it aborts the commit if the newest heading doesn't match — and packages/core/tests/docs/doc-sync-hook.test.ts has a second describe block that re-asserts it in CI.
Run the full pipeline locally: pnpm turbo run lint typecheck test build.

3 — Doc-sync verification (mandatory, not implied by the pipeline run)

Step 2's full pipeline only proves the automated doc-content tests pass — it does not prove every doc mentioning the old version got updated, since several repo docs (DESIGN.md, docs/*) carry version references with no test covering them.

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

27d ago Changed · +1 lines f3fcaadb4744
1mo ago Changed · +7 lines 8e9c2c15b46b
1mo ago Changed · +7 lines 661296187411
2mo ago First seen · 104 lines · 92 tokens per session scan A 2210b711a13d

Subscribe to this mod's changes

release-cut is a skill published in the GitHub repository thomas-powers-jr/cadence (2 stars, last pushed yesterday), licensed MIT. It adds 92 tokens to every session and 1,656 once invoked, about $0.0004 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 agentic-ai ai ai-agents cli code-quality developer-tools

release-cut next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
release-cutthomas-powers-jr/cadence	Skill	2	yesterday	MIT	A	92	Claude Code
git-workflowericrisco/rsc-harness	Skill	503	2d ago	MIT	A	127	Claude Code, Codex
synthetic-release-notestheinfosecguy/razin	Skill	16	13d ago	MIT	A	15	Claude Code, Codex
cli-forge-githubDestynova2/cli-code-skills	Skill	5	2mo ago	MIT	A	165	Claude Code
cli-git-conventionalDestynova2/cli-code-skills	Skill	5	2mo ago	MIT	A	128	Claude Code
github-repo-managementraphaelmansuy/edgecrab	Skill	93	3mo ago	none	A	47	Claude Code, Codex
rea-changelog-updatemorluto/rea	Skill	435k	yesterday	MIT	A	33	Claude Code

cadence: Skill for Claude Code