bump-release

Automate Rust release workflows with semantic version bumps and GitHub releases.

3|Updated Oct 25, 2025
One-click install
npx skills add https://github.com/codekiln/langstar --skill bump-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-release
Source: https://github.com/codekiln/langstar/tree/main/.claude/skills/bump-release
Command: npx skills add https://github.com/codekiln/langstar --skill bump-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git-cliff, gh, cargo, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines the complex and error-prone process of releasing Rust projects. It automates version bumping, changelog generation, Git tagging, and GitHub release creation based on Conventional Emoji Commits, saving you hours of manual work and ensuring consistent releases.

Core Features & Use Cases

  • Semantic Versioning: Automatically determines MAJOR, MINOR, or PATCH version bumps by analyzing commit messages following Conventional Emoji Commits.
  • Changelog Generation: Generates a formatted changelog section using git-cliff and updates the CHANGELOG.md file.
  • GitHub Release Integration: Creates annotated Git tags and publishes a GitHub Release with the generated changelog, including pre-release options.
  • Use Case: After a series of feat and fix commits, use this skill to automatically create the next v1.2.0 release, update Cargo.toml, generate the changelog, and publish it to GitHub.

Quick Start

Create a new release for the project, automatically determining the version bump and publishing to GitHub.

Frequently Asked Questions about bump-release

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

FAQPage Schema
How do I automate Rust project releases with semantic versioning?

Automate Rust releases by analyzing Conventional Emoji Commits to determine semantic version bumps, update Cargo.toml, generate a changelog with git-cliff, create annotated Git tags, and publish to GitHub—all in one workflow.

Can I generate a changelog automatically from my commit history?

Yes, this Skill uses git-cliff to analyze commits since the last release and generates a formatted changelog section that updates your CHANGELOG.md file automatically.

What do I need to set up before running an automated release?

You need git, gh (GitHub CLI), git-cliff, python3, and cargo installed; a repository with Conventional Emoji Commits; and valid GitHub credentials for creating releases.

Does this work with monorepos or workspace projects?

Yes, the Skill updates Cargo.toml across all workspace members during the release, supporting both single-crate and monorepo Rust projects.

Can I test a release without publishing to GitHub?

Yes, the Skill supports dry-run and local-only modes, letting you validate version bumps, changelog generation, and tagging before pushing to GitHub.

What commit message format does this Skill expect?

This Skill requires Conventional Emoji Commits, which use emoji prefixes and structured messages (e.g., feat:, fix:) to automatically determine MAJOR, MINOR, or PATCH version bumps.