skills.rest
kreuzberg-dev
kreuzberg-devOFFICIAL
Explore all skills by this author →
WebsiteGitHub

release-procedure

Guide alef maintainers through GitHub release cutting, tagging, and publishing.

91|16|Updated Mar 31, 2026
Search Tags:#changelog#release#rust#version bump#git tagging#github releases#ci verification
One-click install
npx skills add https://github.com/kreuzberg-dev/alef --skill release-procedure
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release-procedure
Source: https://github.com/kreuzberg-dev/alef/tree/main/.ai-rulez/skills/release-procedure
Command: npx skills add https://github.com/kreuzberg-dev/alef --skill release-procedure

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or inconsistent releases by providing an end-to-end, verification-first checklist for cutting, tagging, and publishing an alef version with correct changelog and synchronized version numbers.

Core Features & Use Cases

  • Release readiness and safety checks: Runs pre-flight build and tests to ensure the release only ships when the repo is healthy.
  • Changelog and version correctness: Requires moving entries from Unreleased into a dated release section and updates Cargo.toml, alef.toml, and ALEF_REV in lockstep via the Taskfile.
  • Linting, atomic commit hygiene, and verified publishing: Enforces a prek lint pass, a single atomic release commit, and uses gh release create so GitHub release automation is triggered correctly.

Quick Start

Tell your release manager to run the full pipeline steps for a new alef version, starting with confirming the working tree and CI health, then updating CHANGELOG.md, setting the version via task set-version, linting with prek, committing chore(release): X.Y.Z, creating the annotated tag, and publishing with gh release create.

Frequently Asked Questions about release-procedure

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

FAQPage Schema
How do I cut and publish a GitHub release with a synchronized Cargo version bump?▼

To cut a GitHub release, you update Cargo.toml and Taskfile versions in lockstep, move changelog entries to a dated section, commit with chore(release), tag the commit, and use gh release create to trigger publishing automation.

What is the best way to ensure changelog integrity before creating a git tag?▼

Ensuring changelog integrity requires moving entries from the Unreleased section into a dated release section within CHANGELOG.md, verifying content accuracy before executing the atomic chore(release) commit and git tagging steps.

How do I automate version updates across Cargo.toml and project configuration files?▼

Automate version updates by running the task set-version command, which synchronizes version numbers across Cargo.toml, alef.toml, and ALEF_REV variables in lockstep to prevent inconsistent release states.

Do I need to run lint checks before publishing a Rust crate to GitHub Releases?▼

Yes, running a prek lint pass is required before publishing to ensure code quality, followed by an atomic release commit and gh release create to verify the tag and trigger GitHub release automation correctly.

What pre-flight checks are needed before cutting a new software release tag?▼

Pre-flight release checks involve confirming the working tree is clean, verifying CI health, running build and test suites, and executing lint checks to ensure the repository is healthy before tagging.

How do I handle a hotfix tag for an unexpected production release?▼

Handling a hotfix tag involves creating a targeted version bump, adding a dated changelog section for the fix, executing lint verification, and publishing the hotfix release using gh release create with tag verification.

Related Skills

Explore More Software Engineering Skills→
BlackBeltTechnologyBlackBeltTechnology
3

release-cut

Automate local release preparation by updating CHANGELOG.md, bumping package.json, and pushing version tags.

Official
Advanced
mr-daedaliummr-daedalium
107

land-and-deploy

Merge PRs, trigger deployment, and verify canary health in CI/CD pipelines.

Community
Advanced
agentty-xyzagentty-xyz
29

release

Coordinate version bumps, changelog updates, verification, tagging, and pushes for Rust/Cargo releases.

Official
Advanced
jim60105jim60105
21

bump-version

Automate semantic version bumps, changelog generation, and Git tagging.

Community
Advanced