opi-release

Automates Rust workspace releases including builds, publishing to GitHub Releases and crates.io.

5|2|Updated May 19, 2026
One-click install
npx skills add https://github.com/OdradekAI/opi --skill opi-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: opi-release
Source: https://github.com/OdradekAI/opi/tree/main/.claude/skills/opi-release
Command: npx skills add https://github.com/OdradekAI/opi --skill opi-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the release process for the opi Rust workspace, ensuring that all necessary steps are followed and that the release is safe and secure.

Core Features & Use Cases

  • Version Control: Bumps version numbers and manages tags.
  • Automated Checks: Performs pre-flight checks, including file presence, git state, CI status, code quality, security, dependencies, and release metadata.
  • Changelog Generation: Automatically generates a changelog based on commit history.
  • Build and Publish: Builds and publishes the workspace to GitHub Releases and crates.io with phased safety gates.
  • Cross-Compilation: Supports cross-compilation for different platforms.
  • Finalization and Verification: Finalizes the release and performs post-release verification.

Quick Start

Run the 'opi-release' skill with the target version number, e.g., 'opi-release 0.7.0'.

Frequently Asked Questions about opi-release

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

FAQPage Schema
How do I automate the release process for a Rust workspace?

You can automate Rust workspace releases by running this Skill with a target version number. It handles version bumping, pre-flight checks, changelog generation, building, and publishing to GitHub Releases and crates.io with phased safety gates.

What automated checks are needed before publishing a Rust workspace to crates.io?

Pre-release validation for a Rust workspace requires checking file presence, git state, CI status, code quality, security, dependencies, and release metadata. This Skill performs these automated checks as safety gates before allowing any build or publish operations.

How do I automatically generate a changelog from commit history for a GitHub release?

You can generate a changelog from commit history automatically as part of the release workflow. This Skill parses your Rust workspace's git commit history to compile the changelog before building and publishing to GitHub.

Can I cross-compile a Rust workspace for different platforms during release?

Yes, cross-compilation for different platforms is supported during the build and publish phase. This Skill integrates cross-compilation into the release pipeline, building Rust workspace binaries for required target platforms before publishing.

Do I need GitHub access to automate Rust workspace publishing?

Yes, GitHub access is required. This Skill needs workspace and GitHub repository access to automate version control, manage tags, and publish the final build artifacts to GitHub Releases and crates.io.