release

Coordinate crate releases and tagging for cryochamber.

32|3|Updated Feb 22, 2026

Search Tags:#automation #git #release #cargo #tagging #crates.io #version-bump

Ready to run

npx skills add https://github.com/GiggleLiu/cryochamber --skill release-giggleliu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/GiggleLiu/cryochamber/tree/main/.claude/skills/release
Command: npx skills add https://github.com/GiggleLiu/cryochamber --skill release-giggleliu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a structured guide for preparing and publishing a new crate release, including determining the appropriate version bump and tagging the release.

Core Features & Use Cases

Step-by-step release workflow covering version bump decisions, clean-state verification, tagging, and publishing to crates.io.
Built-in checks and CI-friendly steps to ensure releases are reproducible and auditable.
Real-world scenario: you need to release a patch that fixes a bug and update the version, push the tag, and publish to crates.io.

Quick Start

Run the release workflow by executing make release V=x.y.z after updating the version in Cargo.toml.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate crate releases and tagging in Rust?▼

Automate crate releases and tagging by running a structured workflow that verifies a clean working tree, applies version bumps in Cargo.toml, commits changes, pushes git tags, and publishes to crates.io.

How do I determine the correct version bump for a crate release?▼

Determine the correct version bump using predefined rules that evaluate commit history and changes, deciding whether to apply a major, minor, or patch increment before updating Cargo.toml.

What's the best way to ensure a clean working tree before publishing to crates.io?▼

Ensure a clean working tree before publishing to crates.io by running built-in checks that verify no uncommitted changes exist, making releases reproducible and auditable.

How do I publish a patched crate update to crates.io?▼

Publish a patched crate update by updating the version in Cargo.toml, running the release workflow to commit and tag the changes, and executing the automated publish sequence to push the crate to crates.io.

Can I run crate version bumps and tagging in a CI pipeline?▼

Run crate version bumps and tagging in CI pipelines using CI-friendly steps designed for reproducible release sequences, ensuring automated checks pass before publishing to crates.io.

Why should I use an automated release workflow for crates instead of manual git tagging?▼

Automated release workflows prevent human error by enforcing clean-state verification, consistent version bump decisions, proper commits, and tagged releases, which manual git tagging lacks.