release

Automate AllBeads release workflows with version bumps, quality gates, and Homebrew updates.

8|1|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/thrashr888/AllBeads --skill release-thrashr888
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/thrashr888/AllBeads/tree/main/.claude/skills/release
Command: npx skills add https://github.com/thrashr888/AllBeads --skill release-thrashr888

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release management for AllBeads is complex, requiring coordination across crates, tags, and external adapters. This skill automates versioning, gating, and publication to GitHub and Homebrew, reducing manual toil.

Core Features & Use Cases

  • Version bumping and semantic tagging across multi-repo Beads ecosystem
  • Quality gate orchestration (fmt, lint, tests) before publish
  • Homebrew tap update and release publishing automation

Quick Start

Provide the target version or confirm the auto-increment choice, then trigger the release workflow to begin.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate git release workflows with version bumps and tagging?

Automate git release workflows end-to-end including version bumps, semantic tagging, quality gate enforcement, and pushing. This process coordinates multi-repo versioning and downstream pipelines across crates, handling both standard and prerelease versioning in diverse git workflows.

What is the best way to automate Homebrew tap updates when publishing a new release?

Automate Homebrew tap updates by directly integrating the release workflow with GitHub and Homebrew pipelines. The automation handles tap updates and release publishing simultaneously after version bumps and quality checks pass.

How do I enforce quality checks before publishing a cargo crate to GitHub?

Enforce quality checks before publishing cargo crates by orchestrating formatting, linting, and testing gates within the release workflow. The process requires direct integration with Cargo.toml and halts publication if these quality gates fail.

Can I use this automation for prerelease versioning across submodules and downstream pipelines?

Yes, this automation supports both standard and prerelease versioning across submodules and downstream pipelines. It applies to release workflows coordinating cargo crates, managing version bumps and tags throughout the diverse git workflow ecosystem.

Do I need direct integration with Cargo.toml and Git to trigger the release workflow?

Yes, direct integration with Cargo.toml, Git, GitHub, and Homebrew workflows is required. You provide the target version or confirm an auto-increment choice, then trigger the release workflow to begin the end-to-end automation process.