release

Cut and publish GitHub-hosted Rust workspace releases with changelogs and test reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates and enforces a safe, repeatable release process for the repository to eliminate manual errors during version bumps, changelog generation, report collection, tagging, and CI-driven publishing.

Core Features & Use Cases

  • Pre-flight Validation: Runs repository checks such as switching to main, pulling latest, running cargo test, cargo clippy, and building docs to prevent broken releases.
  • Report and Artifact Generation: Produces a detailed test report, a traceability matrix, and a changelog (via git-cliff), updates Cargo.toml versions, and collects release artifacts into reports/.
  • Automated Publishing: Commits release changes, creates and pushes a v-tag to trigger CI, and relies on the workflow to build platform binaries and create the GitHub Release with attached reports and pre-release handling.

Quick Start

Run the release skill with the target version (for example v0.3.0) to generate reports, update versions, tag the repository, and trigger CI to publish the release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate Rust workspace releases with Cargo version bumps and changelog generation?

Automate Rust workspace releases by running pre-flight checks, updating Cargo.toml versions, generating changelogs via git-cliff, and pushing a v-tag to trigger CI-driven binary builds and GitHub Release publishing.

Can I use git-cliff to generate a changelog and traceability matrix for a GitHub release?

Yes, git-cliff generates the changelog while the process simultaneously produces a traceability matrix and test report, collecting all release artifacts into a reports directory before publishing the GitHub release.

What's the best way to prevent broken releases in a Rust CI workflow?

Prevent broken releases by enforcing pre-flight validation that switches to main, pulls latest changes, runs cargo test, executes cargo clippy, and builds documentation before proceeding with version bumps or tagging.

Does this release automation process handle tagging and pushing to trigger CI workflows?

Yes, the process commits release changes, creates a version tag, and pushes it to the repository, relying on the CI workflow to build platform binaries and create the GitHub Release with attached reports.

How do I cut a traceable CI-built release for a GitHub-hosted Rust project?

Cut a traceable release by validating the repository, generating test reports and traceability matrices, updating versions in Cargo.toml, and pushing a tag to trigger CI workflows that build and publish the final binaries.