release

Name: release
Availability: InStock
Author: everruns

Automate version bumping, changelog generation, and publish-readiness checks for Rust crates.

12|Updated May 27, 2026

Search Tags:#automation #release #rust #homebrew #ci #crates.io

Ready to run

npx skills add https://github.com/everruns/yolop --skill release-everruns

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/everruns/yolop/tree/main/.agents/skills/release
Command: npx skills add https://github.com/everruns/yolop --skill release-everruns

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, cargo.

What problem does it solve?

This Skill removes the manual overhead and risk of human error involved in cutting a new software release, ensuring consistent versioning, changelog generation, and publish-readiness verification.

Core Features & Use Cases

Automated Release Preparation: Mechanically generates changelogs from git history and validates versioning against project specifications.
Publish-Readiness Checks: Performs dry-run publishing to crates.io to catch dependency drift or packaging errors before they reach production.
Use Case: When a developer is ready to ship a new version, this skill orchestrates the entire process from bumping the version in Cargo.toml to monitoring the final deployment on crates.io and the Homebrew tap.

Quick Start

Invoke the release skill to prepare and verify a new version of the yolop agent for publication.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate Rust CLI version bumping and changelog generation for crates.io?▼

To automate Rust CLI version bumping and changelog generation, this skill coordinates extracting git history and updating Cargo.toml to prepare releases. It validates versioning against project specifications and monitors final deployment to crates.io.

How does publish-readiness verification work for Rust packages before deployment?▼

Publish-readiness verification works by performing dry-run publishing to crates.io to catch dependency drift or packaging errors before production. This mechanism ensures your Rust package meets deployment requirements prior to release.

Do I need GitHub CLI and cargo to automate end-to-end release management?▼

Yes, you need GitHub CLI and cargo to automate release management. The process requires git, gh, and cargo to execute versioning, PR creation, and CI monitoring tasks necessary for consistent deployment to crates.io and Homebrew.

What is the best way to coordinate Homebrew tap and crates.io publishing in CI?▼

The best way to coordinate Homebrew tap and crates.io publishing is automating the end-to-end release lifecycle within Rust-based CLI development. This approach ensures consistent deployment by orchestrating versioning, dry-run checks, and PR creation.

Why does my automated release workflow fail during crates.io dependency drift checks?▼

Automated release workflows fail during crates.io dependency drift checks when packaging errors or dependency mismatches are detected during the dry-run phase. This verification mechanism intentionally catches issues before production deployment.

Can I use this release automation skill for non-Rust projects?▼

No, you cannot use this release automation skill for non-Rust projects. It operates within the context of Rust-based CLI development, relying on cargo to execute versioning and deploy to Rust-centric registries like crates.io.