release-bump-changelog

Create a release commit combining marketing copy with GitHub-generated notes for Rust cargo projects.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/jrmatherly/spacebot --skill release-bump-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-bump-changelog
Source: https://github.com/jrmatherly/spacebot/tree/main/.claude/skills/release-bump-changelog
Command: npx skills add https://github.com/jrmatherly/spacebot --skill release-bump-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release workflows often separate marketing copy, GitHub-generated notes, and version tags, which leads to mismatched changelogs, scattered release context, and manual synchronization. This Skill consolidates those steps into a single, repeatable workflow so release narratives and machine-generated notes land together in CHANGELOG.md and the release commit.

Core Features & Use Cases

  • Synchronized Release Commit: Generates a launch-style marketing story from the actual change set and ensures the generated GitHub release notes are upserted into CHANGELOG.md alongside the version bump.
  • Automated Tagging and Notes: Invokes the repository's cargo bump / release-tag script to generate GitHub-native release notes and create the annotated tag in one operation.
  • Use Case: Maintainers preparing a patch, minor, or major release who need consistent marketing copy, accurate GitHub notes, and an auditable changelog entry in a single commit.

Quick Start

Draft a concise marketing paragraph summarizing why the release matters and invoke cargo bump with that marketing copy file so the tag, generated GitHub notes, and CHANGELOG.md are created together.

Frequently Asked Questions about release-bump-changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate changelog updates and GitHub release notes for a Rust cargo project?

Automate changelog updates and GitHub release notes by generating a launch-style marketing story from your changes and invoking a cargo bump script to upsert GitHub-generated notes into CHANGELOG.md alongside the version bump tag.

What's the best way to combine marketing copy and machine-generated release notes into one commit?

Combining marketing copy and machine-generated release notes into one commit requires drafting a marketing paragraph and passing it to a release-tag script that synchronizes the narrative, GitHub notes, and version bump into a single auditable commit.

Do I need the gh CLI to generate GitHub release notes in my changelog?

Yes, generating GitHub release notes in your changelog requires an authenticated gh CLI, a configured git origin or SPACEBOT_RELEASE_REPO environment variable, and the repository's cargo bump release-tag script.

Can I use this release bump workflow for patch, minor, and major version updates?

Yes, this release bump workflow applies to Rust projects using cargo where maintainers prepare patch, minor, or major version bumps and want the changelog, tag, and release copy created together.

Why does my release workflow have mismatched changelogs and scattered release context?

Release workflows have mismatched changelogs and scattered context when marketing copy, GitHub-generated notes, and version tags are separated into different manual steps instead of synchronized into a single release commit.

How do I create an auditable release commit with synchronized changelog entries?

Create an auditable release commit by drafting a concise marketing paragraph summarizing why the release matters and invoking cargo bump with that marketing copy file so the tag, generated GitHub notes, and CHANGELOG.md are created together.