Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
wu529778790 avatar

Release Notes Generator

  • 400 installs
  • Updated June 24, 2026
  • wu529778790/shenzjd-skills

Helps with productivity & planning tasks.

About

release-notes-generator is a Claude Code skill for productivity & planning. It helps solo builders move faster with AI-assisted coding.

  • release-notes-generator
  • Productivity & Planning
  • AI-coding skill

Release Notes Generator by the numbers

  • 400 all-time installs (skills.sh)
  • +60 installs in the week ending Jul 27, 2026 (Skillselion tracking)
  • Ranked #807 of 3,282 Productivity & Planning skills by installs in the Skillselion catalog
  • Data as of Jul 27, 2026 (Skillselion catalog sync)
npx skills add https://github.com/wu529778790/shenzjd-skills --skill release-notes-generator

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs400
Last updatedJune 24, 2026
Repositorywu529778790/shenzjd-skills

What it does

Helps with productivity & planning tasks.

Files

SKILL.mdMarkdownGitHub ↗

Release Notes Generator

打 tag 时自动对比代码变更,生成标准化的 Release Notes。

Overview

对比上一个 tag 到当前 HEAD 的 git 历史,按 conventional commit 分类(feat/fix/docs/refactor/chore),自动检测 breaking changes,生成标准化的 Release Notes。可选创建 git tag 和 GitHub Release。

When to Use

  • User wants to create a tag or release
  • User wants to summarize version changes
  • User mentions changelog, release notes, or version documentation
  • User inputs /release-notes
  • User wants to generate a CHANGELOG.md from commit history
  • User wants to prepare a release with categorized changes
  • User wants to auto-detect breaking changes before release
  • User wants to create an annotated git tag with release notes

When NOT to Use:

  • User only wants to view git log
  • User wants to modify existing release notes
  • User wants to generate changelogs for multiple repositories (different tooling)
  • User wants to automate release notes in CI/CD (consider semantic-release or release-please)

Core Pattern

Step 1: 检测版本号

获取最新 tag(git describe --tags --abbrev=0),用户指定版本号或根据变更类型建议:有 breaking changes → major,有新功能 → minor,只有 bugfix → patch。

Step 2: 对比变更

PREV_TAG=$(git describe --tags --abbrev=0)
git log ${PREV_TAG}..HEAD --oneline
git diff ${PREV_TAG}..HEAD --stat

Step 3: 分类变更

类别前缀说明
🚀 Featuresfeat:新功能
🐛 Bug Fixesfix:修复
📝 Documentationdocs:文档
♻️ Refactorrefactor:重构
🔧 Choreschore:构建/工具/配置
⚡ Performanceperf:性能优化
🧪 Teststest:测试
🔒 Securitysecurity:安全修复
💥 Breaking ChangesBREAKING CHANGE! 后缀破坏性变更

Breaking Changes 检测规则: 1. commit 消息包含 BREAKING CHANGE:BREAKING CHANGES: 2. commit 类型后带 !(如 feat!:fix!:) 3. commit body 中包含破坏性变更说明

读取 commit 消息中的 conventional commit 前缀,没有前缀的根据文件变更推断。

Step 4: 生成 Notes

使用 templates/release-notes.md 模板生成,包含版本号、日期、分类变更列表、diff 链接。

Step 5: 创建 Tag/Release(可选)

询问用户是否创建 annotated tag 和 GitHub Release。用本 skill 生成的 notes 作为 release body:

# 创建 annotated tag
git tag -a "$TAG" -m "$TAG"

# 创建 GitHub Release,使用生成的 release notes
gh release create "$TAG" --title "$TAG" --notes-file release-notes.md

Quick Reference

/release-notes              # 交互式,自动建议版本号
/release-notes v1.1.0       # 指定版本号
/release-notes --dry-run    # 只生成不创建 tag
参数说明默认值
version版本号自动建议
--dry-run只生成不创建false

Common Mistakes

错误正确做法原因
只看 commit 数量分析实际代码变更commit 数量不代表变更规模
忽略 breaking changes重点标注 💥用户需要知道不兼容变更
不分类,全部列在一起按 feat/fix/docs 分组可读性差
notes 太长精简为关键变更 + diff 链接用户不需要看每个细节
没有前缀的 commit 直接忽略根据文件变更推断类型不是所有团队都严格使用 conventional commits
版本号跳过 semver 规则遵循 major.minor.patch 语义随意编号导致依赖管理混乱
不检查 breaking changes 的 API 影响标注受影响的接口和迁移方式用户升级后才发现破坏性变更
Release Notes 不包含 diff 链接添加 ${PREV_TAG}...${TAG} 对比链接方便用户查看具体代码变更

Related skills

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.