release-skill

release-skill is a skill for Claude Code from Azzygoatcoder/agent-useful-skills. It costs 83 tokens per session (1,440 once invoked), scanned A, original, MIT.

A release checklist for publishing a new software version. It covers changing the version number, creating a Git tag, and publishing a GitHub Release.

In plain words
What is it for?
It helps prepare patch, minor, major, and release-candidate versions, then release them directly or through a fork pull request based on push access.
Why use it?
It reduces mistakes when releasing, such as using the wrong version, tagging the wrong branch, or overlooking a plugin version in a monorepo—a repository containing multiple related projects.

Skill for Claude Code

Written for Claude Code: Claude Code plugin machinery.

Part of the dev-workflow plugin — 4 skills shipped together

Good fit It helps prepare patch, minor, major, and release-candidate versions, then release them directly or through a fork pull request based on push access.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/azzygoatcoder/agent-useful-skills/release-skill
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 Azzygoatcoder/agent-useful-skills --skill release-skill
Clone the repo
git clone --depth 1 https://github.com/Azzygoatcoder/agent-useful-skills

Made for: Claude Code.

Or install dev-workflow, the plugin that ships this one along with the rest of its 4 skills.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/azzygoatcoder/agent-useful-skills/release-skill"><img src="https://agentmods.dev/badge/skills/azzygoatcoder/agent-useful-skills/release-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 83 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,440 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.00083 $0.01440
Opus 5 $0.00042 $0.00720
Sonnet 5 $0.00017 $0.00288
Haiku 4.5 $0.00008 $0.00144

Measured 8d ago against content hash 33c1daa2f5b8, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

release-skill 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 8d 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.

plugins/dev-workflow/skills/release-skill/SKILL.md · 82 lines

How it starts

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

Release — 发版本工作流

半自动发版本:定版本 → bump → tag → GitHub Release。按仓库类型分流。

第 0 步:场景判定(看 push 权限,不看仓库归属)

一句话判据:git remote -v 看 origin 是「权威仓库」还是「你的 fork」。

origin 是 你的角色 场景
权威仓库(你能 push,别人从这拉) Owner / Maintainer A. 直推
你的 fork(权威在 upstream) Contributor B. fork-PR

有 push 权限 → A;无 → B。默认 A。同一个人对不同 repo 角色不同,每次按判据现判。

通用准备

  • gh CLI 已登录;工作区干净
  • 版本号在 pyproject.toml[project] version = "X.Y.Z");有包 __init__.py__version__ 要同步——monorepo 可能只有 pyproject、无 __init__,跳过即可
  • monorepo 有插件plugins/*/.claude-plugin/plugin.json):bump 根版本时顺带查各插件 version 是否与各自 README changelog 同步(失配例子:code-security-skills 曾 plugin.json 1.3.1 vs changelog 1.4.0),见 VERSIONING.md
  • 默认分支用 git rev-parse --abbrev-ref HEAD 判(master / main 皆可,别硬编码)

场景 A:自有仓库直推(默认)

  1. 定版本:读 pyproject.toml 当前版本 + git tag --list 看上次 tag;按 commit 增量建议
    • Patch(X.Y.Z+1):bug 修复 / 安全补丁 / 小文档
    • Minor(X.Y+1.0):新特性 / 无破坏重构
    • Major(X+1.0.0):破坏性变更(0.x 少见)
    • RC 后缀(v0.2.0-rc9):可去 RC(v0.3.0)或加 RC 号(v0.2.0-rc10)
  2. bump:改 pyproject.toml(+ 有 __init__ 则同步);版本已对就跳过。monorepo 时顺带查各插件 plugin.json version 是否 stale(改了哪个插件的 skills 就 bump 哪个)
  3. tag + release
    git tag -a vX.Y.Z -m "vX.Y.Z"
    git push origin vX.Y.Z
    gh release create vX.Y.Z --title "vX.Y.Z — 一句话主题" --notes-file notes.md
    
    • notes 用 git log <last-tag>..HEAD --oneline 汇总,按主题分组(核心重构 / 打包 / 特性 / 文档)

场景 B:上游贡献(fork-PR-CI 完整流程)

  1. 定版本:同上(读 pyproject + __init__,问用户,建议增量)
  2. bump:改两处 → git commit -m "chore: bump version to X.Y.Z"
  3. release PR
    git checkout -b release/vX.Y.Z
    git push fork release/vX.Y.Z -u
    git checkout <default-branch> && git reset --hard origin/<default-branch>
    gh pr create --title "chore: bump version to X.Y.Z" --base <default-branch> --head <fork-owner>:release/vX.Y.Z --body "..."
    
    • PR body 含 "Changes since ",逐条列 merged PR
  4. CIgh pr checks <pr>;失败不 merge,先修
  5. merge + tag
    gh pr merge <pr> --merge --delete-branch
    git pull origin <default-branch>
    git tag -a vX.Y.Z -m "vX.Y.Z"
    git push origin vX.Y.Z
    
  6. GitHub Releasegh release create vX.Y.Z --title ... --notes-file notes.md(非 RC 写全面 notes,RC/patch 只列上次 tag 后的 PR)
  7. README 版本:更新版本 badge(当前版本:**vX.Y.Z**),docs-only 直接推
  8. cleanupgit branch -d release/vX.Y.Z

Read the full file on GitHub · 82 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. 8d ago First seen · 82 lines · 83 tokens per session scan A 33c1daa2f5b8

Subscribe to this mod's changes

release-skill is a skill published in the GitHub repository Azzygoatcoder/agent-useful-skills (6 stars, last pushed 10d ago), licensed MIT. It adds 83 tokens to every session and 1,440 once invoked, about $0.0004 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

dsh-changelog

A release-note writing guide for maintaining a CHANGELOG, a file that records what changed in each software version. It follows Keep a Changelog categories and semantic versioning rules.

hackerFish/awesome-dsh-skills · 30 tokens

dsh-plugin-publish

A publishing procedure for putting a DSH plugin on GitHub and adding it to the DSH community list. DSH is the plugin ecosystem described by the procedure, and GitHub is the code-hosting service where the plugin is published.

hackerFish/awesome-dsh-skills · 51 tokens

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…

addyosmani/agent-skills · 74 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 · 33 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