release

Coordinate Rust release workflows with release-plz, cargo-dist, and cocogitto.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jmagar/rust-bin --skill release-jmagar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/jmagar/rust-bin/tree/main/.claude/skills/release
Command: npx skills add https://github.com/jmagar/rust-bin --skill release-jmagar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill orchestrates the end-to-end release workflow for Rust projects, ensuring a clean state, validated plans, and deterministic tagging before publishing.

Core Features & Use Cases

  • Release planning & validation: verifies plan correctness with release-plz, checks CI parity locally, and ensures changelog entries align with conventional commits.
  • Version bump & changelog automation: walks through version bumps and changelog updates, applying them to the repository.
  • Tagging & publishing: drives git tagging and pushing, coordinating cargo-dist and GitHub Release creation.

Quick Start

Run the end-to-end release workflow to validate a clean state, generate a release plan, and push the new tag.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate Rust release workflows with version bumps and changelogs?

Automate Rust release workflows by coordinating release-plz to validate release plans, apply version bumps, update changelogs, and push git tags. The process enforces a clean working tree and runs local CI checks before tagging to ensure deterministic publishing.

What is the best way to validate a release-plz plan before pushing a new tag?

Validate a release-plz plan by enforcing a clean working tree, running local CI checks to verify parity, and checking that changelog entries align with conventional commits. This ensures the release plan is correct before applying version bumps and pushing tags.

Does this release automation workflow require a clean git working tree?

Yes, the release automation workflow requires a clean git working tree before proceeding. It enforces this clean state, runs local CI gate validations, and verifies the release-plz plan to ensure deterministic and safe tag pushing across branches.

Can I use cargo-dist and cocogitto together for Rust project releases?

Yes, you can coordinate cargo-dist and cocogitto together for Rust project releases. The workflow uses cocogitto for conventional commit validation and tagging, while cargo-dist handles the build and GitHub Release creation coordination.

How do I ensure changelog entries align with conventional commits before a Rust release?

Ensure changelog alignment with conventional commits by using release-plz to validate the release plan during the workflow. The process checks CI parity locally and verifies that generated changelog entries correctly match the conventional commit history before tagging.

Why does my Rust release workflow fail before pushing a new git tag?

Rust release workflows fail before pushing tags if the working tree is not clean, local CI checks do not pass, or the release-plz plan validation fails. The workflow gates tag operations behind these checks to prevent invalid releases.