菜单
When the user needs to write release notes, changelogs, or document what changed in a release. Use when the user says 'write release notes,' 'changelog,' 'what changed,' 'document this release,' 'update the README after launch,' or after completing a significant feature or version bump.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/0xranx/agentbrief --skill release-notes命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Learn from corrections, mistakes, and discoveries during conversations. When the user corrects you, when something fails unexpectedly, or when you discover a project-specific pattern worth remembering — record it as a learning so future sessions benefit automatically.
When the user wants to draft tweets, plan threads, post to Twitter/X, or manage their Twitter presence
When reviewing UI/UX for quality, consistency, and polish. Use when the user says 'review the design,' 'check the UI,' 'does this look good,' 'design audit,' 'UX review,' or 'polish the frontend.' Also use after implementing any user-facing feature to catch visual and interaction issues before shipping.
基于 SOC 职业分类
正在显示 SKILL.md
| name | release-notes |
| description | When the user needs to write release notes, changelogs, or document what changed in a release. Use when the user says 'write release notes,' 'changelog,' 'what changed,' 'document this release,' 'update the README after launch,' or after completing a significant feature or version bump. |
You are a technical writer creating release documentation. Your goal is to communicate changes clearly to different audiences: users who want to know what's new, developers who need migration guidance, and stakeholders who need the executive summary.
Start by analyzing what changed:
# Get commits since last release
git log --oneline v$(previous)..HEAD
# Get changed files for scope assessment
git diff --stat v$(previous)..HEAD
Categorize each change:
User-facing release notes (blog/email):
Developer changelog (CHANGELOG.md):
Internal release summary (Slack/team):
## [1.2.0] - 2025-03-15
### Added
- Feature X: one-sentence description (#123)
### Changed
- **BREAKING**: API endpoint `/v1/foo` renamed to `/v2/foo`. See migration guide below.
### Fixed
- Fixed crash when input contained unicode characters (#456)
### Migration Guide
If you used `/v1/foo`, update to `/v2/foo`. The request format is unchanged.