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`.
67
81%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Passed
No findings from the security scan
Create a version bump commit where each release section includes both:
v0.2.0 narrative (clear positioning + concrete highlights).marketing_file="$(mktemp)"$marketing_filecargo bump <patch|minor|major|X.Y.Z> with marketing copy input:
SPACEBOT_RELEASE_MARKETING_COPY_FILE="$marketing_file" cargo bump <...>scripts/release-tag.sh.gh api .../releases/generate-notes).CHANGELOG.md with:
### Release Story (from your marketing file)CHANGELOG.md in the release commit.git show --name-only --statCargo.toml, Cargo.lock (if present), and CHANGELOG.md.git tag --list "v*" --sort=-v:refname | head -n 5).gh CLI installed and authenticated (gh auth status).origin remote points to GitHub, or set SPACEBOT_RELEASE_REPO=<owner/repo>.SPACEBOT_SKIP_MARKETING_COPY=1.Use markdown only (no outer ## vX.Y.Z heading; script adds it). Recommended structure:
Avoid vague hype. Tie claims to concrete shipped changes.
CHANGELOG.md is seeded from historical releases and then maintained by the release bump workflow.ab2c160
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.