release-prep

Automate Rust release workflows by bumping versions, validating changes, and opening pull requests.

1|Updated Jan 24, 2026
One-click install
npx skills add https://github.com/dataroadinc/rhusky --skill release-prep-dataroadinc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-prep
Source: https://github.com/dataroadinc/rhusky/tree/main/.claude/skills/release-prep
Command: npx skills add https://github.com/dataroadinc/rhusky --skill release-prep-dataroadinc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Prepare a release pipeline that systematically bumps versions, runs quality checks, and creates a PR to publish a new release.

Core Features & Use Cases

  • Pre-release checks: ensure formatting, linting, and tests pass before releasing.
  • Version management: bump the version in Cargo.toml and align changes across files.
  • PR-driven release: push changes and open a PR, with CI tagging and publishing after merge.

Quick Start

Initiate a release workflow by bumping the version, running tests, and opening a pull request on your main branch.

Frequently Asked Questions about release-prep

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

FAQPage Schema
How do I automate a Rust release workflow with Cargo version bumping and PR creation?

To automate a Rust release workflow, you can bump the Cargo version, run pre-release checks like formatting and linting, and open a pull request. This ensures version management and test verification happen before merging.

What is PR-driven release publishing for Rust projects?

PR-driven release publishing pushes version changes to a branch and opens a pull request. After the PR merges, CI handles Git tagging and publishing, automating the release pipeline systematically.

Does this release preparation process run tests before bumping the Cargo version?

Yes, the release preparation process runs pre-release checks to ensure formatting, linting, and tests pass. It bumps the version in Cargo.toml and aligns changes across files only after validating the project.

Can I use this workflow to align version numbers across multiple files in a Rust project?

Yes, you can use this workflow to manage versions by bumping the version in Cargo.toml. It systematically aligns the updated version numbers across related files before pushing the changes.

What's the best way to trigger CI tagging after a version bump in Git?

The best way to trigger CI tagging is to push the version bump to a branch and open a pull request. Once the PR is merged into the main branch, the CI pipeline automatically handles the Git tagging.