What is release-workflow?

A release checklist covering change logs, README updates, version numbers, commits, pushes, tags, and release notes.

Use it when preparing and publishing a software release, including checking tests, feature references, and project counts.

It helps prevent code from being released with missing documentation or stale project information.

How savant0x/savant-code configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to savant0x/savant-code. 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/savant0x/savant-code/main/.agents/skills/release-workflow/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/savant0x/savant-code

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/savant0x/savant-code/release-workflow/github.svg)](https://agentmods.dev/skills/savant0x/savant-code/release-workflow)

Your own site

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

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

When invoked 1,024 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.

Model	Per session	Once invoked
Fable 5.1	$0.00013	$0.01024
Opus 5.5	$0.00005	$0.00410
Sonnet 5.5	$0.00003	$0.00205
Haiku 4.5	$0.00001	$0.00102

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

Security

Grade A, and why

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

.agents/skills/release-workflow/SKILL.md · 97 lines

How it starts

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

Release Workflow Standards (Savant-Code)

When to Use

For any version bump, release, resume, or release-readiness check in Savant-Code. Releases flow exclusively through the public-release pipeline (scripts/public-release.ts; docs: docs/public-release.md).

Procedure

Open the version heading at bump time — when the version bump lands (bun run version:bump), open ## <version> — <YYYY-MM-DD> in CHANGELOG.md and write release notes directly beneath it as each change closes. Never accumulate an ## Unreleased section — the release engine (extractChangelogSection) requires exactly one version heading matching the release version; Unreleased content never ships in notes.
Audit phase before push — run the gate battery and fix everything red: bun run typecheck (all workspaces), bun run test, bun x eslint . --max-warnings 0, bun run lint:md, bun run validate:repository, bun run version:check, plus the generated-doc drift checks (generate:provider-docs:check, generate:protocol-bundle:check).
Preview — bun run release:public:preview (read-only plan: identity, version metadata, CHANGELOG section extraction; never mutates).
Diagnose — bun run release:public:diagnose (read-only full gate manifest with evidence; investigate failures here).
Release — SAVANT_CODE_RELEASE_AUTOMATION=1 bun run release:public (automation) or interactive bun run release:public. The engine commits, tags, pushes main + tag, creates the GitHub release from the extracted changelog section, and publishes the scoped npm packages (default CLI-only; SDK opt-in via SAVANT_CODE_RELEASE_PACKAGES).
Failure mid-transaction → fix the cause, then bun run release:public:resume with the same package scope.

Never push code without the version heading + notes in CHANGELOG.md and the README checked against the release. Never release outside the pipeline.

Read the full file on GitHub · 97 lines

Files

What ships with it

2 files 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.

1mo ago Changed · +9 lines 2f5cae857fc4
1mo ago Changed · +18 lines · -10 tokens per session 3893cff43ff7
2mo ago First seen · 70 lines · 23 tokens per session scan A a1f04bc9e454

Subscribe to this mod's changes

release-workflow is a skill published in the GitHub repository savant0x/savant-code (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,024 once invoked, about $0.0001 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.

Git and workflow Releases

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 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

savant-code: Skill for Claude Code