What problem does it solve? Publishing a Rust crate or binary release involves irreversible external writes, SemVer and MSRV decisions, packaging pitfalls, and supply-chain signing requirements, and a single mistake can leak tokens or ship broken artifacts. ## Core Features & Use Cases - Release gating workflow: Walks through SemVer classification with cargo-semver-checks, MSRV and feature-matrix verification, manifest metadata checks, and cargo package inspection before any publish. - Binary distribution and signing: Covers reproducible builds, checksum manifests, SBOMs, SLSA provenance, cosign blob signing, and consumer-side verification of uploaded assets. - Recovery and workspace ordering: Provides yank, crate deletion, owner-change, and RustSec advisory procedures plus ordered multi-package workspace publishing. - Use Case: You are about to publish version 2.1.0 of a crate from a workspace. The skill has you diff against the previous tag, run the API and MSRV checks, dry-run the whole package set, request explicit authorization, publish once, then verify the registry and tag the exact commit. ## Quick Start Ask the agent to prepare and publish version 1.4.0 of your crate to crates.io following the rust-crate-release checklist, starting with the read-only release checks.
