release

Name: release
Availability: InStock
Author: CodingThrust

Automate Rust crate releases with SemVer versioning and crates.io publishing.

35|7|Updated Jan 9, 2026

Search Tags:#ci/cd #versioning #release #rust #semver #crates.io

Ready to run

npx skills add https://github.com/CodingThrust/problem-reductions --skill release-codingthrust

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/CodingThrust/problem-reductions/tree/main/.claude/skills/release
Command: npx skills add https://github.com/CodingThrust/problem-reductions --skill release-codingthrust

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill simplifies the process of preparing and publishing new releases for Rust crates, ensuring versioning consistency and a clean release state.

Core Features & Use Cases

Version Bumping: Guides through SemVer for patch, minor, or major version increments.
State Verification: Ensures tests and linting pass before release.
Automated Release: Executes release commands, commits, tags, and pushes changes.
Use Case: When you've completed a new feature for the problemreductions crate, use this Skill to correctly bump the version, run all checks, and publish the new release to crates.io.

Quick Start

Use the release skill to prepare a new patch version release for the current crate.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate Rust crate publishing to crates.io?▼

You can automate Rust crate publishing by using this skill to manage SemVer version bumping, verify build and linting status, and execute release commands including tagging and pushing to your repository via CI for crates.io.

What is the best way to handle SemVer version bumps for Rust releases?▼

Handling SemVer version bumps for Rust releases requires guiding through patch, minor, or major version increments. This skill automates that process, correctly updating your crate version and ensuring tests pass before committing changes.

Can I verify tests and linting pass before publishing a new crate version?▼

Yes, you can verify tests and linting pass before publishing a new crate version. This skill performs state verification to ensure all checks succeed before executing release commands and pushing the new version to your repository.

Does this release automation process handle git tagging and pushing?▼

Yes, the release automation process handles git tagging and pushing. It executes release commands, commits the version bump, creates the necessary tags, and pushes changes directly to your repository as part of the publishing workflow.

When do I need to use an automated release workflow for Rust crates?▼

You need an automated release workflow for Rust crates when you have completed a new feature and want to ensure versioning consistency. It is used to correctly bump the SemVer version, run checks, and publish to crates.io without manual errors.