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

release-bump-changelog

GitHub

用于发布版本升级和更新变更日志。根据实际代码变更生成营销风格的发布故事，并结合 GitHub 生成的原生发布说明，通过 cargo bump 工具将两者整合写入 CHANGELOG.md，确保技术细节与市场叙事同步更新。

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

Trigger Scenarios

准备进行软件版本发布需要更新项目的变更日志撰写发布说明和市场宣传文案

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.