write-release-notes
Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes for a version (e.g. "write release notes for v1.32.0", "generate release notes for the latest release", "create changelog for v2.0").
- License 许可
- Apache-2.0
- 所属仓库
- KaiavN/anvilcode
- 最近更新
- 2026-07-07
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- write-release-notes
- description
- Generate engaging, high-energy release notes for a given version tag. Fetches the release from GitHub, retrieves every linked PR's title and description, then synthesizes all changes into a polished, user-facing release note with an enthusiastic tone. Use when the user asks to write, generate, or create release notes for a version (e.g. "write release notes for v1.32.0", "generate release notes for the latest release", "create changelog for v2.0").
02 资源文件 2
03 SKILL.md 正文
Write Release Notes
Generate compelling, high-energy release notes by pulling live data from GitHub and synthesizing every PR into a cohesive narrative.
Workflow
1. Fetch Release Data
Run the bundled script to pull the release metadata and all linked PR details in one shot:
bash .anvil/skills/write-release-notes/scripts/fetch-release-data.sh <version> [owner/repo]
<version>: The release tag (e.g.v1.32.0)[owner/repo]: Optional. Defaults to the current repo detected viagh repo view.
The script outputs two sections:
### RELEASE METADATA ###— tag name, publish date, release name, raw body### PR DETAILS ###— one JSON object per PR with:number,title,body,labels,author,mergedAt,url
2. Categorize Changes
Group PRs by their conventional commit prefix or label:
| Category | Prefixes / Labels |
|---|---|
| Features | feat, type: feature |
| Bug Fixes | fix, type: fix |
| Performance | perf |
| Refactors | refactor |
| Maintenance | chore, docs, ci, build, deps |
Dependency bumps (e.g. Dependabot PRs) go into Maintenance. Skip PRs with error: "not found".
3. Write the Release Notes
Produce a Markdown document with the following structure. Keep the tone exciting, punchy, and developer-friendly — celebrate wins, highlight impact, and make readers feel the momentum.
# [Product Name] [Version] — [Punchy Tagline]
> One-sentence hook that captures the spirit of this release.
## What's New
[2-4 sentence narrative that weaves together the biggest features and fixes.
Speak to impact, not implementation. Use active voice. Be enthusiastic.]
## Highlights
### [Feature/Fix Category]
**[PR Title rephrased as user benefit]** ([#NNN](url))
[1-2 sentences expanding on the PR description. Focus on what the user gains.
If the PR body has useful context, distill it. If empty, infer from the title.]
[Repeat for each significant PR — skip pure chores/dep bumps unless noteworthy]
## Bug Fixes & Reliability
[Bullet list of fixes, each with a brief impact statement and PR link]
## Under the Hood
[Brief paragraph or bullet list covering refactors, maintenance, and dep updates —
keep it light, acknowledge the work without boring the reader]
## Contributors
A huge thank you to everyone who made this release happen: [list @handles — exclude bots like @dependabot]
---
**Full changelog**: [GitHub Release link]
4. Tone & Style Guidelines
- Lead with value: "You can now..." beats "We added..."
- Be specific: Name the feature, not just the category
- Use energy words: "blazing", "seamless", "rock-solid", "powerful", "finally"
- Short paragraphs: Max 3 sentences per block
- Skip internal jargon: Translate crate names and internal concepts into plain language
- Celebrate contributors: Name them enthusiastically
- Tagline formula:
[Version] — [Adjective] [Theme](e.g. "v1.32.0 — Smarter Config, Smoother Workflows") - No implementation details: Do not mention internal module names, struct names, function names, crate names, or how something was implemented. Focus purely on what the user experiences or gains.
5. Contributors Filter
Only include external contributors in the Contributors section — exclude the core team:
@tusharmath@amitksingh1490@laststylebender14- Bots (e.g.
@dependabot)
If no external contributors exist, omit the Contributors section entirely.
6. Validate Length
After writing the release notes, run the bundled validation script to confirm the output is under 2000 characters:
echo "<release notes>" | bash .anvil/skills/write-release-notes/scripts/validate-release-notes.sh
If it prints FAIL, trim the draft and re-run until it prints PASS:
- Remove the Under the Hood section first
- Consolidate Bug Fixes into a shorter bullet list
- Shorten individual PR descriptions to one tight sentence
- Remove the least impactful Highlights entries
7. Output
Print the final release notes directly in the chat. Do not write to a file unless the user explicitly asks.
Notes
- The script handles ANSI color codes injected by
ghCLI automatically. - PRs not found (closed without merge, private, etc.) are silently skipped.
- If the release has no linked PRs in its body, fall back to listing commits between tags:
gh api repos/<owner>/<repo>/compare/<prev_tag>...<version> --jq '.commits[].commit.message'
04 同仓库更多 Skills
github-pr-description
Generate and create pull request descriptions automatically using GitHub CLI. Use when the user asks to create a PR, generate a PR description, make a pull request, or submit changes for review. Analyzes git diff and commit history to create comprehensive, meaningful PR descriptions that explain what changed, why it matters, and how to test it.
execute-plan
Execute structured task plans with status tracking. Use when the user provides a plan file path in the format `plans/{current-date}-{task-name}-{version}.md` or explicitly asks you to execute a plan file.
create-skill
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends your capabilities with specialized knowledge, workflows, or tool integrations.
test-skill
A test skill with resources
minimal-skill
A minimal skill with no resources
resolve-conflicts
Use this skill immediately when the user mentions merge conflicts that need to be resolved. Do not attempt to resolve conflicts directly - invoke this skill first. This skill specializes in providing a structured framework for merging imports, tests, lock files (regeneration), configuration files, and handling deleted-but-modified files with backup and analysis.