release

Automate Rust release workflows with version validation, checks, commit, tag, and push.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/langify-org/ws-cli --skill release-langify-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/langify-org/ws-cli/tree/main/.claude/skills/release
Command: npx skills add https://github.com/langify-org/ws-cli --skill release-langify-org

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the end-to-end release workflow, including version validation, linting, testing, commit, tagging, push, and CI monitoring, reducing manual overhead and human error.

Core Features & Use Cases

  • Version validation: Verify semantic version formatting and consistency across project components.
  • Pre-release checks: Run formatting, linting, tests, and documentation builds to ensure release quality.
  • Release orchestration: Automates commit, tag creation, and push while guarding against unsafe actions when user confirmation is required.
  • Use Case: A Rust project with multiple crates can execute a single command to ensure all checks pass and the release tag is published to the repository.

Quick Start

Provide the version as an argument to the release command, for example: /release 0.5.0

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate Rust project release workflows with semantic versioning and CI checks?

Automating Rust project release workflows involves validating semantic version formatting, running pre-commit lint and test checks, and orchestrating commit, tag, and push operations. This Skill coordinates those end-to-end release steps to reduce manual overhead and human error.

How do I ensure version consistency across multiple Rust crates before tagging a release?

To ensure version consistency across multiple Rust crates, you can validate semantic version formatting and synchronize versions across project components. This Skill performs cross-component synchronization and pre-release checks to verify formatting, linting, tests, and documentation builds.

Can I use automated release orchestration for Rust projects with user-confirmation gating?

Yes, automated release orchestration can include safe user-confirmation gating before committing, tagging, and pushing. This Skill guards against unsafe actions by requiring user confirmation during the release workflow while monitoring CI status across crates and docs.

What is the best way to run pre-commit checks and documentation builds before a Rust release?

The best way to run pre-commit checks is to automate formatting, linting, testing, and documentation builds as part of a multi-step verification process. This Skill automates these pre-release checks to ensure release quality before version validation and tag creation.

How do I trigger an end-to-end release with automated version validation for my Rust project?

You trigger an end-to-end release by providing the target version as an argument, such as specifying version 0.5.0. This initiates the automated workflow, applying version validation, pre-release checks, and safe user-confirmation gating before committing and pushing the release tag.