skills.rest
max-sixty
max-sixtyCOMMUNITY
Explore all skills by this author →
𝕏@max_sixtyGitHub

release

Automate Worktrunk releases with testing, version bumps, changelog updates, and tagging.

6.4k|231|Updated Oct 17, 2025
Search Tags:#git#changelog#versioning#github#release#cargo#ci
One-click install
npx skills add https://github.com/max-sixty/worktrunk --skill release-max-sixty
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/max-sixty/worktrunk/tree/main/.claude/skills/release
Command: npx skills add https://github.com/max-sixty/worktrunk --skill release-max-sixty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing Worktrunk can be error-prone and time-consuming; this Skill standardizes and automates the end-to-end release process.

Core Features & Use Cases

  • Run tests and validations: Execute tests and verifications before a release.
  • Version bump & changelog: Update Cargo.toml with the new version and append a changelog entry.
  • Release orchestration: Commit changes, merge to main, create and push a git tag, and publish a GitHub Release.

Quick Start

Use the release skill to publish a new version after completing feature work and running all tests. Example: "Release v0.3.0 with changes summarized."

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate a Cargo release workflow with changelog and git tagging?▼

Automate a Cargo release workflow by running tests, bumping the version in Cargo.toml, appending a changelog entry, and pushing a git tag. This coordinates CI and GitHub releases end-to-end.

What is the best way to manage patch, minor, and major version bumps in a Rust project?▼

Manage patch, minor, and major version bumps by standardizing the release process to update Cargo.toml and generate changelog entries automatically. This ensures consistent versioning across releases.

Do I need a CHANGELOG file to automate GitHub releases for my repository?▼

Yes, a CHANGELOG file is required to automate GitHub releases. The workflow appends new entries to the changelog during the version bump process before tagging and publishing the release.

Can I include contributor credits when publishing a GitHub release automatically?▼

Yes, you can include contributor credits when publishing a GitHub release. The release orchestration process coordinates CI, contributor credits, and GitHub releases automatically after merging changes.

How does CI coordinate with git tags during an automated version release?▼

CI coordinates with git tags by committing version changes, merging to main, creating a git tag, and pushing it to trigger the GitHub Release. This orchestration ensures the tag matches the published version.

Why are my automated release validations failing before the Cargo.toml version bump?▼

Release validations fail when repository tests are not passing before the version bump. The workflow executes tests and verifications prior to updating Cargo.toml to ensure the release is stable.

Related Skills

Explore More Software Engineering Skills→
datheredathere
3.7k

release-prep

Bump version numbers across qsv files and update the changelog for release preparation.

Official
Advanced
dawsonblockdawsonblock

release

Automate Cargo/Rust release workflows with tests, version bumps, and tag creation.

Community
Advanced
NITRR-OfficialNITRR-Official
4

git-workflow

Manage Git workflow stages including branch naming, commits, pull requests, and merges.

Official
Intermediate
pradyumnasagarpradyumnasagar
6

release-management

Manages ORS skill releases with versioning, changelogs, and marketplace updates.

Community
Intermediate