Agent Skills › spacedriveapp/spacebot › release-bump-changelog

release-bump-changelog

GitHub

用于准备版本发布，基于实际变更生成营销风格发布故事，并调用 cargo bump 脚本将 GitHub 原生发布说明与营销文案合并更新至 CHANGELOG.md，完成版本标记和提交。

.agents/skills/release-bump-changelog/SKILL.md spacedriveapp/spacebot

Trigger Scenarios

需要执行软件版本升级（如 patch/minor/major）时需要更新或生成项目发布说明及 CHANGELOG 文档时

Install

npx skills add spacedriveapp/spacebot --skill release-bump-changelog -g -y

More Options

Non-standard path

npx skills add https://github.com/spacedriveapp/spacebot/tree/main/.agents/skills/release-bump-changelog -g -y

Use without installing

npx skills use spacedriveapp/spacebot@release-bump-changelog

指定 Agent (Claude Code)

npx skills add spacedriveapp/spacebot --skill release-bump-changelog -a claude-code -g -y

安装 repo 全部 skill

npx skills add spacedriveapp/spacebot --all -g -y

预览 repo 内 skill

npx skills add spacedriveapp/spacebot --list

SKILL.md

Frontmatter

{
    "name": "release-bump-changelog",
    "description": "Use this skill when preparing a release bump or updating release notes. It writes a launch-style release story from the actual change set, then runs `cargo bump` so the generated GitHub notes and the marketing copy land together in `CHANGELOG.md`."
}

Release Bump + Changelog

Goal

Create a version bump commit where each release section includes both:

a launch-style narrative (marketing copy)
the exact GitHub-generated release notes

Workflow

Ensure the working tree is clean (except allowed release files).
Draft release story markdown from real changes (PR titles, release-note bullets, and diff themes).
- Target style: similar to the v0.2.0 narrative (clear positioning + concrete highlights).
- Keep it factual and specific to the release.
- Write to a temp file (outside repo is preferred):
  - marketing_file="$(mktemp)"
  - write markdown content to $marketing_file
Run cargo bump <patch|minor|major|X.Y.Z> with marketing copy input:
- SPACEBOT_RELEASE_MARKETING_COPY_FILE="$marketing_file" cargo bump <...>
- This invokes scripts/release-tag.sh.
- The script generates GitHub-native notes (gh api .../releases/generate-notes).
- The script upserts CHANGELOG.md with:
  - ### Release Story (from your marketing file)
  - GitHub-generated notes body
- The script includes CHANGELOG.md in the release commit.
Verify results:
- git show --name-only --stat
- Confirm commit contains Cargo.toml, Cargo.lock (if present), and CHANGELOG.md.
- Confirm tag was created (git tag --list "v*" --sort=-v:refname | head -n 5).

Requirements

gh CLI installed and authenticated (gh auth status).
origin remote points to GitHub, or set SPACEBOT_RELEASE_REPO=<owner/repo>.
Marketing copy is required unless explicitly bypassed with SPACEBOT_SKIP_MARKETING_COPY=1.