release

Validate Rust crate release gates including build, test, lint, and format checks.

1.9k|124|Updated Mar 1, 2026
One-click install
npx skills add https://github.com/yologdev/yoyo-evolve --skill release-yologdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/yologdev/yoyo-evolve/tree/main/skills/release
Command: npx skills add https://github.com/yologdev/yoyo-evolve --skill release-yologdev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides teams to make safe, auditable release decisions for Rust crates, ensuring we publish only when quality checks pass.

Core Features & Use Cases

  • Gate-based readiness: verify build, tests, lints, formatting, and changelog currency before releasing.
  • Versioning and publishing: automatically prepare Cargo.toml, create a git tag, and publish to crates.io when gates pass.
  • Audit trail: document what version is released, why now, and what changes are included.

Quick Start

Prepare a new release by validating all gates and tagging the release if all checks pass.

Frequently Asked Questions about release

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

FAQPage Schema
How do I validate a Rust crate before publishing to crates.io?

Publishing a Rust crate to crates.io requires validating a gate checklist that verifies cargo build, cargo test, cargo clippy, and cargo fmt checks alongside changelog currency to ensure release readiness.

What is release readiness for a Cargo-based project?

Release readiness for a Cargo-based project means passing a defined gate checklist that validates builds, tests, lints, formatting, changelog currency, and documentation before publishing to crates.io.

How do I automate versioning and git tagging for Rust crates?

Automate versioning and git tagging for Rust crates by inspecting Cargo.toml and CHANGELOG.md, passing quality gates, and preparing the version tag automatically before publishing to crates.io.

Does the release process check README and CHANGELOG files before publishing?

Yes, the release process inspects README.md and CHANGELOG.md files to verify documentation validity and changelog currency before allowing a crates.io publish operation to proceed.

What happens if cargo clippy or cargo test fails during crate publishing?

If cargo clippy or cargo test fails during crate publishing, the readiness evaluation returns a REJECT status and provides specific remediation steps to fix the failing quality gates.