writing-release-notes
Generates release notes from merged pull requests, grouping the changes into features, fixes, and chores so the notes read clearly. Use when the user asks to draft release notes, write a changelog, summarize merged PRs into release notes, or any time you need to write something describing recent code changes.
- License 许可
- MIT
- 最近更新
- 2026-06-18
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- writing-release-notes
- description
- Generates release notes from merged pull requests, grouping the changes into features, fixes, and chores so the notes read clearly. Use when the user asks to draft release notes, write a changelog, summarize merged PRs into release notes, or any time you need to write something describing recent code changes.
02 资源文件 3
- 参考文档references/learnings.md1.4 KB
- 参考文档test-prompts.md658 B
- 参考文档tests.md590 B
03 SKILL.md 正文
<!-- DEMO FIXTURE for the learnings-seeding path (improving-skills tests.md).
This SKILL.md carries intentional slop — an over-broad description
catch-all, a duplicated step, a duplicated section, and a filler intro —
all flagged as Status: open candidate edits in references/learnings.md.
/improving-skills should seed those entries and apply them. Do not "fix"
this by hand; it is the input state for a reproducible test. -->
Writing Release Notes
This skill helps you write release notes. Release notes are a document that describes what changed in a release. Writing good release notes is important because users want to know what changed in the new version of the software.
When to use
When the user asks for release notes or a changelog assembled from a set of merged pull requests.
Steps
- Collect the merged pull requests for the release.
- Group each pull request into one of three categories: features, fixes, chores.
- Write a one-line summary for each pull request.
- Group the summaries by category (features, fixes, chores).
- Assemble the grouped summaries into the final document.
Output format
Emit markdown with an H2 heading per category and a bullet per change:
## Features
- <change>
## Fixes
- <change>
## Chores
- <change>
Formatting the notes
Format the output as markdown. Use an H2 heading for each category (Features, Fixes, Chores) and a bullet list of the changes under each heading.
Learnings
Retro observations from real runs live in references/learnings.md.
04 同仓库更多 Skills
generating-ai-ideas
Orchestrates a council of specialized perspectives to generate, stress-test, and refine high-quality, sellable AI-related business and product ideas. Use when the user wants validated AI business opportunities, AI product concepts, or AI tooling ideas with clear go-to-market paths.
reviewing-pull-requests
Reviews a pull request diff against a structured rubric covering correctness, tests, security, and style, then produces a prioritized comment list. Use when the user asks to review a PR, audit a diff, or check changes before merging.
winpath-in-reference
Audits widget docs for path portability. Use when the user asks to audit fixture path portability, scan widget references for backslash paths, or vet doc hygiene.
vague-trigger
Generates widget summaries for engineers and is helpful for data processing tasks generally.
stale-tests
Refreshes widget fixture baselines on demand. Use when the user asks to refresh fixture baselines, re-verify widget scenarios, or rebaseline gizmo outputs.
smell-in-script
Installs the widget toolchain via the bundled script. Use when the user asks to install the widget toolchain, bootstrap gizmo tooling, or set up fixture dependencies.