Agent skill

Release

by 312362115 in 312362115/claude

发版自动化技能:CalVer 版本号 + 从 git log 生成 changelog + GitHub Releases。

MITAuto-check passedDevelopment

Install Release

skills CLI
$ npx skills add 312362115/claude --skill release -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install 312362115/claude release --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/312362115/claude.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/release .claude/skills/release && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
release
GitHub stars
107
Token cost
~874 tokens
SKILL.md length
126 words
Files
1
Skills in repo
20
Repo updated
First seen
Licence
MIT

At a glance

发版自动化技能:CalVer 版本号 + 从 git log 生成 changelog + GitHub Releases。

  • Works in 3 steps: 通知用户:发版完成,输出版本号和 Release URL → 更新 package.json /… → 提醒:如果有需要手动操作的部署步骤,列出来
  • Tasks that involve Changelog and release notes
  • SKILL.md covers 第一步:发版前检查, 第二步:确定版本号, 第三步:生成 Changelog and 第四步:创建 Release, plus 3 more sections
  • Calls git and gh

What it does

Release is an agent skill from 312362115/claude. 发版自动化技能:CalVer 版本号 + 从 git log 生成 changelog + GitHub Releases。 覆盖完整发版流程:版本号生成→changelog 生成→git tag→GitHub Release(或本地 changelog 文件)。 在发版前自动触发 security-audit 安全审查(如果配置了 CI/CD 则检查 CI 状态)。 触发词:发版、发布、release、生成 changelog、打 tag、版本发布。 触发场景:功能开发完成准备发布、用户主动要求发版、里程碑完成。

Its SKILL.md is about 870 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes, Security review and CI/CD. It works with GitHub and Git. The licence is MIT.

When your agent uses it

  • Tasks that involve Changelog and release notes
  • Tasks that involve Security review
  • Tasks that involve CI/CD

Example prompts

  • “/release”

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. 通知用户:发版完成,输出版本号和 Release URL
  2. 更新 package.json / pyproject.toml(如果项目需要版本号同步到配置文件)
  3. 提醒:如果有需要手动操作的部署步骤,列出来

What it can do on your machine

Read from SKILL.md and the folder at commit 2d4fa49. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • gh

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git and gh, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Release loads about 874 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 126 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~874

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from 312362115/claude at commit 2d4fa49, republished under its MIT licence (© 312362115). 126 words, ~874 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
发版自动化技能:CalVer 版本号 + 从 git log 生成 changelog + GitHub Releases。 覆盖完整发版流程:版本号生成→changelog 生成→git tag→GitHub Release(或本地 changelog 文件)。 在发版前自动触发 security-audit 安全审查(如果配置了 CI/CD 则检查 CI 状态)。 触发词:发版、发布、release、生成 changelog、打 tag、版本发布。 触发场景:功能开发完成准备发布、用户主动要求发版、里程碑完成。
version
1.0.0
last_updated
2026-04-08
repository
https://github.com/312362115/claude

发版(Release)

发版不只是打 tag,是一个质量门禁流程:安全审查→生成版本→创建 Release。


第一步:发版前检查

发版前必须确认以下条件:

准备发版
  │
  ├─ 1. 代码状态检查
  │   ├─ 工作区干净?(无未提交改动)
  │   ├─ 在正确的分支上?(main / release branch)
  │   └─ 已合并所有需要的 PR?
  │
  ├─ 2. CI 状态检查(如果有)
  │   └─ GitHub Actions 全绿?
  │
  ├─ 3. 安全审查
  │   └─ 提示用户:是否需要跑 security-audit?(上线服务强烈建议)
  │
  └─ 4. 测试验证
      └─ 核心功能是否经过验证?

检查命令:

bash
# 工作区状态
git status

# CI 状态(GitHub)
gh run list --limit 5

# 未合并的 PR
gh pr list

任何检查不通过,提示用户处理后再继续,不强行发版。


第二步:确定版本号

CalVer 格式
YYYY.MM.PATCH
部分含义示例
YYYY年份2026
MM月份(不补零)4
PATCH当月第几次发布(从 1 开始)1, 2, 3...

版本号生成逻辑:

bash
# 获取当前年月
YEAR=$(date +%Y)
MONTH=$(date +%-m)

# 查找当月已有的最大版本号
LATEST=$(git tag --list "${YEAR}.${MONTH}.*" --sort=-version:refname | head -1)

if [ -z "$LATEST" ]; then
  # 当月第一次发布
  VERSION="${YEAR}.${MONTH}.1"
else
  # 递增 PATCH
  PATCH=$(echo "$LATEST" | awk -F. '{print $3 + 1}')
  VERSION="${YEAR}.${MONTH}.${PATCH}"
fi

echo "版本号: $VERSION"

示例:

  • 2026 年 4 月第 1 次发布 → 2026.4.1
  • 2026 年 4 月第 2 次发布 → 2026.4.2
  • 2026 年 5 月第 1 次发布 → 2026.5.1

第三步:生成 Changelog

从 git log 提取
bash
# 获取上一个 tag 到 HEAD 的所有提交
PREV_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "")

if [ -z "$PREV_TAG" ]; then
  # 没有历史 tag,取所有提交
  COMMITS=$(git log --oneline --pretty=format:"%s")
else
  COMMITS=$(git log ${PREV_TAG}..HEAD --oneline --pretty=format:"%s")
fi
按 type 分组

根据 commit message 的 type(scope): desc 格式自动分组:

markdown
# Changelog — v2026.4.1

## 新功能(Features)
- **auth**: 支持 OAuth2 第三方登录
- **export**: 用户数据导出功能

## 修复(Fixes)
- **login**: 修复密码错误时返回 500 的问题
- **cache**: 修复缓存 key 冲突

## 重构(Refactoring)
- **api**: 统一错误响应格式

## 其他
- **docs**: 更新 API 文档
- **test**: 补充登录模块测试用例

分组规则:

commit typechangelog 分组
feat新功能(Features)
fix修复(Fixes)
refactor重构(Refactoring)
perf性能优化(Performance)
docs, test, chore, ci其他(如果没有 feat/fix/refactor 可省略)
Changelog 输出
  • 有 GitHub:嵌入 GitHub Release 的 body
  • 无 GitHub:写入 docs/changelog/YYYY-MM-DD-v<版本号>.md

第四步:创建 Release

方式 A:GitHub Release(优先)
bash
# 创建 tag
git tag -a "v${VERSION}" -m "Release v${VERSION}"
git push origin "v${VERSION}"

# 创建 GitHub Release
gh release create "v${VERSION}" \
  --title "v${VERSION}" \
  --notes "$(cat <<'EOF'
<changelog 内容>
EOF
)"
方式 B:本地 Changelog 文件

如果项目不在 GitHub 或不需要 GitHub Release:

bash
# 创建 tag
git tag -a "v${VERSION}" -m "Release v${VERSION}"

# 写入 changelog 文件
# 存入 docs/changelog/YYYY-MM-DD-v<版本号>.md

第五步:发版后

  1. 通知用户:发版完成,输出版本号和 Release URL
  2. 更新 package.json / pyproject.toml(如果项目需要版本号同步到配置文件)
  3. 提醒:如果有需要手动操作的部署步骤,列出来

完整发版流程

用户:发个版
  │
  ├─ Step 1: 发版前检查(代码状态 + CI + 安全)
  ├─ Step 2: 生成版本号(CalVer)
  ├─ Step 3: 生成 Changelog(从 git log)
  ├─ Step 4: 创建 Release(GitHub 或本地文件)
  └─ Step 5: 发版后处理

与其他 skill 的关系

task-finish(功能收尾)
  ↓
security-audit(发版前安全审查)
  ↓ 审查通过
release(本 skill — 发版)

© 312362115, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/release of 312362115/claude.

Open the folder on GitHubat commit 2d4fa49

Compare with similar skills

Release next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skill312362115/claude107—~874Automated safety check: PassMIT
Worktrunk Release Workflowmax-sixty/worktrunk9k—~6.9kAutomated safety check: PassCustom licence
Codex Proxy RS Releasezyycn/codex-proxy-rs750—~327Automated safety check: PassApache-2.0
CI Automationjeremylongshore/tons-of-skills-marketplace2.8k—~1.4kAutomated safety check: NotesMIT
Repo SentinelMathews-Tom/armory328—~2.2kAutomated safety check: PassMIT
Release Bumpjamiepine/voicebox57k—~1.1kAutomated safety check: PassMIT

Similar skills

  • Worktrunk Release Workflow

    max-sixty/worktrunk

    Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.

    9k GitHub stars~6.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Codex Proxy RS Release

    zyycn/codex-proxy-rs

    Plans versions, writes release notes, publishes stable or pre-release builds and recovers from failed releases for Codex Proxy RS, without covering deploys or tag cleanup.

    750 GitHub stars~327 tokensUpdated today
    DevelopmentAuto-check passed
  • CI Automation

    jeremylongshore/tons-of-skills-marketplace

    A skill your agent uses when running GitHub Actions locally, creating task runner recipes, generating changelogs from git history, managing GitHub PRs/issues/releases programmatically, or creating…

    2.8k GitHub stars~1.4k tokensUpdated today
    DevelopmentAuto-check: notes
  • Repo Sentinel

    Mathews-Tom/armory

    Full security audit for public repositories across 12 attack surfaces: git history, secrets, CI/CD, containers, dependencies, licenses.

    328 GitHub stars~2.2k tokensUpdated 2 days ago
    SecurityAuto-check passed
  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Official

    Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.

    22k GitHub stars~1.1k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from 312362115/claude

All 20 skills in this repo
  • Diagram

    312362115/claude

    专业图表生成技能:根据需求自动选择合适的图表类型,生成符合设计规范的 PNG 图表. An agent skill from 312362115/claude.

    107 GitHub stars~2.7k tokensUpdated 4 mo ago
    Auto-check passed
  • Deep Research

    312362115/claude

    深度调研技能:对任意命题进行系统性调研并输出专业研究报告. An agent skill from 312362115/claude.

    107 GitHub stars~6.6k tokensUpdated 4 mo ago
    Auto-check passed
  • Preview Md

    312362115/claude

    MD 文件浏览器预览:GitHub 风格渲染 + 左侧自动目录. An agent skill from 312362115/claude.

    107 GitHub stars~636 tokensUpdated 4 mo ago
    Auto-check passed
  • Writing

    312362115/claude

    通用写作技能:以"内容→组件→组合"的方式产出技术文档、产品文档、汇报材料. An agent skill from 312362115/claude.

    107 GitHub stars~1.6k tokensUpdated 4 mo ago
    Auto-check passed
  • Code Walkthrough

    312362115/claude

    代码导读技能:帮助快速理解不熟悉的项目或模块,建立心智模型. An agent skill from 312362115/claude.

    107 GitHub stars~1k tokensUpdated 4 mo ago
    Auto-check: notes
  • DB Review

    312362115/claude

    数据库代码审查 + Migration 安全检查. An agent skill from 312362115/claude.

    107 GitHub stars~1.8k tokensUpdated 4 mo ago
    Auto-check passed

Works with

Categories

Questions about Release

What does Release do?

发版自动化技能:CalVer 版本号 + 从 git log 生成 changelog + GitHub Releases。. Release is an agent skill from 312362115/claude.

When should I use Release?

Release fits situations like: tasks that involve Changelog and release notes; tasks that involve Security review; tasks that involve CI/CD.

How do I install Release in Claude Code?

Run `npx skills add 312362115/claude --skill release -a claude-code`. Or copy the skill folder (skills/release in 312362115/claude) into .claude/skills/release in your project. Claude Code loads it when a task matches its description.

How do I install Release in Codex?

Run `npx skills add 312362115/claude --skill release -a codex`. Or copy the skill folder (skills/release in 312362115/claude) into .agents/skills/release in your project. Codex loads it when a task matches its description.

Can I use Release in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add 312362115/claude --skill release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.

What does Release need to run?

Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git and gh).

Does Release access the network?

SKILL.md contains no URLs. Its commands use git and gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Release safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Release use?

Release is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Release use?

About 874 tokens (SKILL.md is roughly 3.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Release?

Skills that share tags, products or a category with Release: Worktrunk Release Workflow (max-sixty/worktrunk, 9k stars), Codex Proxy RS Release (zyycn/codex-proxy-rs, 750 stars), CI Automation (jeremylongshore/tons-of-skills-marketplace, 2.8k stars) and Repo Sentinel (Mathews-Tom/armory, 328 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

312362115 (a GitHub user) maintains it in 312362115/claude, which has 107 GitHub stars. The repository holds 20 skills in this directory. The repository was last updated on May 14, 2026.

Source: 312362115/claude on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.