release

Automate semantic versioning, Git tags, and crates.io publishing via `just release`.

8|4|Updated Jan 15, 2026
One-click install
npx skills add https://github.com/jscraik/Agent-Skills --skill release-jscraik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/jscraik/Agent-Skills/tree/main/product/ops/release
Command: npx skills add https://github.com/jscraik/Agent-Skills --skill release-jscraik

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of creating and publishing new project releases, ensuring versioning consistency and adherence to safety protocols.

Core Features & Use Cases

  • Automated Versioning: Bumps project version in Cargo.toml according to SemVer.
  • Release Automation: Creates Git tags and publishes to crates.io using just release.
  • Safety Checks: Validates branch, working tree cleanliness, and credentials before proceeding.
  • Use Case: When you need to release a new version of your Rust crate, use this skill to handle the entire process from version bump to publishing.

Quick Start

Use the release skill to create a new project release with version 1.4.2.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate publishing a new Rust crate release to crates.io?

You can automate crate publishing by running the `just release X.Y.Z` command, which bumps your version in Cargo.toml, creates a Git tag, and publishes to crates.io. It validates your working tree and Cargo credentials beforehand to ensure a safe release.

How does semantic versioning work when publishing a new project release?

Semantic versioning for project releases involves specifying a new X.Y.Z version number, which the automation then applies to your Cargo.toml file before creating a Git tag and publishing the package. This ensures versioning consistency across your releases.

What safety checks are needed before creating a Git tag and publishing a crate?

Before creating a Git tag and publishing a crate, the process validates your current Git branch, checks that the working tree is clean, and verifies your Cargo credentials. These checks prevent accidental or inconsistent releases.

How do I bump the version in Cargo.toml for a new release without manual edits?

To bump the version in Cargo.toml automatically, execute the `just release X.Y.Z` command with your desired semantic version. The process handles the file update directly, then proceeds to tag and publish the release.