prepare-release

Create a pre-release branch, update Cargo dependencies, draft release notes, and open a pull request.

231|130|Updated Jul 22, 2015
One-click install
npx skills add https://github.com/coreos/afterburn --skill prepare-release-coreos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepare-release
Source: https://github.com/coreos/afterburn/tree/main/.opencode/skills/prepare-release
Command: npx skills add https://github.com/coreos/afterburn --skill prepare-release-coreos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Preparing a release often requires creating a dedicated branch, updating dependencies, drafting release notes from recent commits, and opening a pull request; this Skill automates and standardizes those repetitive, error-prone steps so maintainers can focus on reviewing changes rather than performing mechanical tasks.

Core Features & Use Cases

  • Create pre-release branch: checks main is up to date and creates pre-release-X.Y.Z from main.
  • Dependency management: detects unintended Cargo.toml lower-bound changes, runs cargo update, and commits updated Cargo.lock.
  • Release notes drafting: analyzes commits since the last tag, filters noise, classifies entries into Major/Minor/Packaging, and updates docs/release-notes.md.
  • PR automation: pushes the branch and opens a GitHub pull request with a standardized body for reviewers.
  • Use case: maintainers of Rust/Cargo projects who want a reproducible, checklist-driven pre-release workflow that reduces manual mistakes and speeds up release preparation.

Quick Start

Run the prepare-release workflow with the target version and optional next version, for example: /prepare-release 5.11.0 --next 5.12.0

Frequently Asked Questions about prepare-release

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

FAQPage Schema
How do I automate release preparation for a Rust Cargo project?

Automating release preparation for a Rust Cargo project involves creating a pre-release branch, updating dependencies, drafting release notes from commit history, and opening a pull request. This Skill standardizes those repetitive steps to reduce manual mistakes.

Can I automatically generate release notes from Git commit history?

You can automatically generate release notes from commit history by analyzing commits since the last tag, filtering noise, classifying entries into Major, Minor, or Packaging, and updating docs/release-notes.md for the release.

What do I need to run a Cargo release workflow and open a GitHub PR?

To run an automated Cargo release workflow and open a GitHub PR, you need the cargo and gh CLIs installed, an up-to-date main branch, and a GitHub-hosted repository to push the pre-release branch.

Does this automation check for unintended dependency changes before a release?

Yes, the release automation checks for unintended dependency changes by detecting unintended lower-bound modifications in Cargo.toml and running cargo update to commit a synchronized Cargo.lock file.

What is the best way to draft release notes and classify commits for a version bump?

The best way to draft release notes and classify commits for a version bump is to analyze commit history since the last tag, filter noise, and categorize entries into Major, Minor, or Packaging updates before opening a PR.