dotagent:release

Automate version bumps, CHANGELOG updates, git tagging, and crates.io publishing for Rust workspaces.

3|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/avelino/dotagent --skill dotagent-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dotagent:release
Source: https://github.com/avelino/dotagent/tree/main/.claude/skills/release
Command: npx skills add https://github.com/avelino/dotagent --skill dotagent-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill streamlines the release process for a multi-crate Rust workspace, automatically coordinating version bumps, CHANGELOG updates, git tagging, and crate publishing to crates.io.

Core Features & Use Cases

  • Version bump propagation across all workspace crates.
  • CHANGELOG management at the top level with proper entry formatting.
  • Tagged releases and publishing to crates.io in dependency-aware order.
  • Preflight checks and validation steps before publishing to ensure a clean main branch.

Quick Start

Say 'release X.Y.Z' to start the end-to-end release workflow.

Frequently Asked Questions about dotagent:release

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

FAQPage Schema
How do I automate Rust workspace releases with version bumps and crates.io publishing?

Automate Rust workspace releases by coordinating version bump propagation across all crates, updating the top-level CHANGELOG, creating git tags, and publishing to crates.io in a dependency-aware order.

What is the best way to publish multi-crate Rust workspaces in dependency order?

Publishing multi-crate Rust workspaces in dependency order requires a workflow that resolves inter-crate dependencies, ensuring predictable publish sequencing to crates.io without version conflicts.

How does a Rust release workflow handle CHANGELOG updates and git tagging?

A Rust release workflow handles CHANGELOG updates by formatting top-level entries automatically, while simultaneously creating git tags to mark the release version across the entire workspace.

Can I use an automated release workflow for Rust projects with dependent crates?

You can use this workflow for Rust workspace projects with dependent crates, as it applies dependency-aware version bumping and ensures a predictable publish order to crates.io.

What preflight checks are needed before publishing a Rust crate to crates.io?

Preflight checks before publishing to crates.io ensure a clean main branch and validate the workspace state, preventing failed publishes or inconsistent versioning across dependent crates.