- name
SKILL.md
技能文件保留在发布者的仓库中。
在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add ratel-ai/ratel --skill changelog -a cursor -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add ratel-ai/ratel --skill changelog -a claude-code -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add ratel-ai/ratel --skill changelog -a codex -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add ratel-ai/ratel --skill changelog -a grok -y在 Grok Bot 聊天中发送复制的消息。Bot 会从 GitHub 获取这个 SKILL.md,并添加到你所有 Bot 共享的技能中。
Install this skill: https://github.com/ratel-ai/ratel/tree/HEAD/.claude/skills/changelog来自发布者
Updates a release unit's CHANGELOG.md in preparation for tagging it. Ratel releases
per unit (ADR-0008): each unit ships on its own tag (<prefix>-v*) at its own version.
For workflow-wired units, .github/workflows/release.yml rejects a tag whose unit CHANGELOG
doesn't contain the version being released. vercel-ai-sdk is temporarily published
manually via scripts/publish-rc.sh; still run this skill before its tag even though the
workflow gate does not cover it yet.
Run it once per unit you're releasing.
The units and their manifests/CHANGELOGs live in one registry —
scripts/release-units.mjs — which every release tool reads. Run node scripts/release-units.mjs --list
for the authoritative set; the current ten units are:
@ratel-ai/mcp-server lives in ratel-ai/ratel-mcp and maintains its own CHANGELOG there.
If the user hasn't named the unit, run node scripts/releasable.mjs — it lists which
units have commits since their last release tag. Pick the unit $UNIT being released.
Read its canonical version:
node scripts/release-units.mjs --version "$UNIT" # -> $TARGET
If the user supplies a different version explicitly, prefer that and warn them the working tree disagrees.
The range is from the unit's own last release tag to HEAD:
prefix=$(node scripts/release-units.mjs --tag-prefix "$UNIT")
FROM=$(git describe --tags --match "${prefix}*" --abbrev=0 2>/dev/null || true)
If $FROM is empty the unit has never shipped; the whole history is in range.
bash .claude/skills/changelog/draft.sh --unit "$UNIT"
It emits a single ### <package-name> block for the unit, containing either
Keep-a-Changelog sections (### Added, ### Fixed, ### Changed) or the sentinel
_No user-facing changes._. (Omit --unit to draft every unit at once.) With no
<from-ref> argument the script ranges each unit from its own last tag automatically.
If draft.sh exits 127, git-cliff is missing. Tell the user how to install it (the
script's stderr already does), and stop.
Inspect $TARGET, and edit only this unit's CHANGELOG:
RC (X.Y.Z-rc.N): prepend a new section above the most recent versioned section:
## [X.Y.Z-rc.N] - YYYY-MM-DD
<draft content for the unit, or the sentinel>
Use today's date in YYYY-MM-DD (UTC).
GA (no -rc suffix): enter GA-collapse mode:
## [X.Y.Z-rc.*] section already present that matches the same
MAJOR.MINOR.PATCH as $TARGET.### Added, ### Changed, ### Fixed)
with the new draft entries from step 3 (commits since the last RC tag)._No user-facing changes._ sentinel if any real entries exist; keep it only
if the unioned set is empty.## [X.Y.Z] - YYYY-MM-DD section
containing the merged content.## [0.1.4]) untouched.Show the unit's CHANGELOG pending changes in the conversation. Ask the user to confirm or edit. Common curation moves:
cliff.toml's skip rules).Once approved, write only this unit's CHANGELOG using the Edit tool. Do not commit.
The release commit is the user's responsibility — they typically include the CHANGELOG
alongside the version bump in a single release: <unit>-vX.Y.Z commit.
If releasing more than one unit, repeat from step 1 for each.
Tell the user:
<unit>-v<version> tag + push.release.yml tag-version-check job verifies the unit's
CHANGELOG contains the tag version; if it doesn't, the release is blocked.vercel-ai-sdk, publish manually with scripts/publish-rc.sh after the tag push; its
CHANGELOG is not workflow-gated yet.YYYY-MM-DD in UTC.### Added, ### Changed, ### Fixed, ### Removed, ### Deprecated, ### Security. Omit empty subsections._No user-facing changes._ for a unit with no in-scope commits.## [Unreleased] at the top — it stays empty between releases.ADR 0008 (docs/adr/0008-release-engineering.md) records the per-unit tag/version split, the
CHANGELOG mechanism, and the rationale. Read it if you're unsure why something is structured
the way it is.
Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation co
---name: changelogdescription: Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package)…---# .claude/skills/changelog/SKILL.md概览
Update per-package CHANGELOG.md files for a Ratel release. Drafts entries with git-cliff (scoped per package), lets you curate, then writes the CHANGELOGs. Handles both RC entries and GA-graduation collapse (merging X.Y.Z-rc.* sections into a single X.Y.Z section). Invoke before tagging a release.
常见问题
从发布者处下载 .claude/skills/changelog/SKILL.md,或复制路径后打开仓库。PlugMCP 只收录该技能,不托管文件。
发布者将它存放在 https://github.com/ratel-ai/ratel。
Claude、Cursor、Codex 和 Grok Build 可以读取你从发布者仓库添加的 SKILL.md。在聊天中发送技能的 GitHub 文件夹链接,Grok Bot 就会安装它。