Changelog 自动生成

changelog-gen

Changelog 生成器 - 从 Git 历史自动生成 CHANGELOG

laolaoshiren/claude-code-skills-zh·0installs876starsGit & Pull Requests

SKILL.md

Full skill instructions

Changelog 自动生成

触发条件

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

工作流程

第 1 步：获取 Git 历史

# 获取上一个 tag 到 HEAD 的所有提交
git log --oneline --since="$(git describe --tags --abbrev=0)" HEAD

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

第 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

判断依据：

提交信息含 BREAKING CHANGE: 或 type 后加 !（如 feat!:）→ 主版本
存在 feat 提交 → 次版本
仅 fix/docs/chore 等 → 修订版本

第 4 步：生成 CHANGELOG

输出格式

# Changelog

## [1.3.0] - 2026-06-17

### ⚠️ Breaking Changes
- 移除废弃的 `/api/v1/users` 端点，统一使用 `/api/v2/users` (#130)

### ✨ 新功能
- 新增用户认证模块 (#123)
- 支持 OAuth2 登录 (#124)
- 新增批量导出功能 (#128)

### 🔒 安全修复
- 升级 lodash 修复原型污染漏洞 CVE-2025-XXXX (#129)

### 🐛 Bug 修复
- 修复分页查询偏移量错误 (#125)
- 修复并发写入导致的数据竞争 (#127)

### ⚡ 性能优化
- 优化大列表渲染性能，减少 50% 内存占用 (#126)

### 📝 文档
- 更新 API 文档 (#131)

### 📦 依赖更新
- 升级 axios 1.6.0 → 1.7.0 (#132)

注意事项

Breaking Changes 必须放在最前面，加粗突出显示
每条记录关联 Issue/PR 编号，便于追溯
安全修复需注明 CVE 编号（如有）
版本号应与 git tag 保持一致
如果是预发布版本，使用 -beta.1、-rc.1 后缀
可维护一个 CHANGELOG.md 文件，每次 release 追加到顶部

Install skill

Copy and run in your terminal

npx -y skills add https://github.com/laolaoshiren/claude-code-skills-zh --skill changelog-gen

View on GitHub

changelog-gen

More Git & Pull Requests skills

View all

Git & Pull Requests

requesting-code-review

Dispatch code review subagents with focused context to catch issues before they compound.

295.4K 245.8K

View

Git & Pull Requests

receiving-code-review

Evaluate code review feedback with technical rigor before implementing, avoiding performative agreement and blind implementation.

295.4K 208.8K

View

Git & Pull Requests

using-git-worktrees

Isolated git worktrees with smart directory selection and safety verification.

295.4K 205.2K

View

Git & Pull Requests

finishing-a-development-branch

Structured workflow for completing development branches with test verification and merge/PR options.

295.4K 202.3K

View

Git & Pull Requests

Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.

101.4K 55.6K

View

Git & Pull Requests

git-commit

Standardized git commits using Conventional Commits specification with intelligent diff analysis and message generation.

39.7K 46.4K

View

Git & Pull Requests

git-workflow-and-versioning

Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, or when you need to organize work across multiple parallel streams.

101.4K 44.2K

View

Git & Pull Requests

ponytail-review

Code review focused exclusively on over-engineering. Finds what to delete: reinvented standard library, unneeded dependencies, speculative abstractions, dead flexibility. One line per finding: location, what to cut, what replaces it. Complements correctness-focused review, this one only hunts complexity.

155.5K 32.1K

View

Git & Pull Requests

excalidraw-diagram-generator

Generate Excalidraw diagrams from natural language descriptions in multiple formats.

39.7K 31.1K

View

Git & Pull Requests

ponytail-audit

Whole-repo audit for over-engineering. Like ponytail-review, but scans the entire codebase instead of a diff: a ranked list of what to delete, simplify, or replace with stdlib/native equivalents. One-shot report, does not apply fixes.

155.5K 30K

View