发版前写 release notes 很容易临时翻 git log，然后漏掉 breaking change 或迁移说明。这个场景适合做成 Skill。
目标
让 agent 根据 git diff、commit、PR 标题，整理出稳定格式的发布说明。
SKILL.md 草稿
---
name: release-notes
description: Generate release notes from git history, merged PRs, and changed files. Use before tagging a release or publishing a changelog.
---
# Release Notes
Collect:
1. User-facing changes
2. Bug fixes
3. Breaking changes
4. Migration steps
5. Known risks
6. Verification commands
Output:
## Highlights
## Changes
## Fixes
## Breaking Changes
## Migration
## Verification
我会加的规则
Do not include internal refactors unless they affect users or operators.
If a migration is required, put it in Breaking Changes or Migration.
If tests were not run, say so explicitly.
使用方式
Use release-notes to summarize changes since v1.2.0. Read commits and changed files.
如果项目有 GitHub PR，可以再加：
Group changes by PR and preserve links.
为什么值得做成 Skill
release notes 的格式应该稳定，否则每次发版都像重新写作文。
固定格式之后，团队成员看起来也舒服：哪些是功能、哪些是修复、有没有 breaking change，一眼能扫到。
1 个帖子 - 1 位参与者
来源: LinuxDo 最新话题查看原文