Changelog Gen

This automates changelog generation from your Git commit history using Conventional Commits conventions. It pulls commits since the last tag, categorizes them by type (feat, fix, docs, refactor, perf, test, chore), and outputs a nicely formatted Markdown changelog with emoji indicators and version headers. Saves you from manually sorting through git log output when you're ready to cut a release. The workflow is straightforward: it reads your commits, groups them into sections like new features and bug fixes, and structures everything under version numbers with dates. Works best if your team already follows commit message conventions, otherwise you'll get a mixed bag of categorization.

GitHub stars: 328
last updated: May 13, 2026

View on GitHub

Install

$ npx -y skills add laolaoshiren/claude-code-skills-zh --skill changelog-gen --agent claude-code

Installs into .claude/skills of the current project.

Files

Changelog 自动生成

触发条件

当用户要求生成 changelog、更新日志、版本记录、release notes 时激活此技能。

工作流程

第 1 步：获取 Git 历史

# 先获取最近的 tag，再用 revision range 查询
git describe --tags --abbrev=0
git log --oneline <last-tag>..HEAD

# 或指定范围
git log --oneline v1.0.0..HEAD

# 仓库没有 tag 时，明确选择起始提交或查看全部历史
git log --oneline

第 2 步：分类提交

按 Conventional Commits 分类：

分类	Type 标识	图标
新功能	`feat`	✨
Bug 修复	`fix`	🐛
文档	`docs`	📝
重构	`refactor`	♻️
性能优化	`perf`	⚡
测试	`test`	🧪
构建/工具	`chore`	🔧
Breaking Changes	含 `BREAKING CHANGE:` 或 `!`	⚠️
安全修复	`fix(security)` 或含 CVE	🔒
依赖更新	`deps` 或 `chore(deps)`	📦

第 3 步：版本号确定策略

遵循 Semantic Versioning 规则：

变更类型	版本变化	示例
Breaking Changes	主版本 +1	1.2.0 → 2.0.0
新功能 (feat)	次版本 +1	1.2.0 → 1.3.0
Bug 修复 (fix)	修订版本 +1	1.2.0 → 1.2.1
安全修复 (fix(security))	修订版本 +1（紧急发布）	1.2.0 → 1.2.1