菜单
Generate changelog entries for alcatraz releases following Common Changelog conventions. Use when preparing a release, writing changelogs, creating release notes, or when user mentions release-note, changelog, or release preparation.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | release-note |
| description | Generate changelog entries for alcatraz releases following Common Changelog conventions. Use when preparing a release, writing changelogs, creating release notes, or when user mentions release-note, changelog, or release preparation. |
| user_invocable | true |
Generate a changelog entry for an alcatraz release in docs/changelogs/v{VERSION}.md.
v0.3.0). If omitted, detect the next version using svu next.If a version argument was provided, use it (strip leading v for the heading, keep it for the filename).
If no version was provided, run:
svu next
If svu is not available, ask the user for the version.
Weight determines sort order in the docs site (newer versions sort first).
Formula: -(major × 100 + minor × 10 + patch). Examples:
Run these commands to understand what changed since the last release:
# Find the last release tag
git describe --tags --abbrev=0
# Commits since last tag (one-line format)
git log $(git describe --tags --abbrev=0)..HEAD --oneline
Read individual commits (via git show) as needed when writing entries — don't bulk-diff upfront.
Read the most recent existing changelog for style reference:
ls docs/changelogs/v*.md
Read the latest one to match formatting conventions exactly.
Include only user-facing changes:
Exclude:
Classify into categories (in this order, only include non-empty):
Each entry must be:
../config/fields.md)Entry format:
- Brief imperative description ([`abcdef0`](https://github.com/bolasblack/alcatraz/commit/abcdef0))
```toml
# Code example if applicable
Additional context. See Relevant Docs.
### Step 7: Generate the File
Write `docs/changelogs/v{VERSION}.md` with this structure:
```markdown
---
title: v{VERSION}
weight: {WEIGHT}
---
## [{VERSION_NO_V}] - {YYYY-MM-DD}
### Added
- Entry 1 ...
- Entry 2 ...
[{VERSION_NO_V}]: https://github.com/bolasblack/alcatraz/releases/tag/v{VERSION}
Do NOT commit the changelog file. After generating, tell the user:
make release-minormake release-patchmake release-majorflake.nix version, commits, tags, and pushesmake release-notes runs in .github/workflows/release.yml)../config/fields.md not absolute URLs. Hugo resolves them via BookPortableLinks. make release-notes converts them to absolute URLs for GitHub Releases.