skills.rest
Agent-Clubhouse
Agent-ClubhouseOFFICIAL
Explore all skills by this author →
WebsiteGitHub

prepare-beta

Prepare a beta release for a Workshop plugin by gathering commits, classifying changes, and creating a PR.

2|2|Updated Feb 17, 2026
Search Tags:#git#plugin#release-management#pull-request#version-bump#beta-release
One-click install
npx skills add https://github.com/Agent-Clubhouse/Clubhouse-Workshop --skill prepare-beta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: prepare-beta
Source: https://github.com/Agent-Clubhouse/Clubhouse-Workshop/tree/main/.claude/skills/prepare-beta
Command: npx skills add https://github.com/Agent-Clubhouse/Clubhouse-Workshop --skill prepare-beta

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Beta-release coordination for Clubhouse plugins is manual and error-prone. This skill automates gathering commits, classifying changes, proposing version bumps, and creating PRs with precise tag instructions, saving time and reducing mistakes.

Core Features & Use Cases

  • Phase-driven workflow: 6 phases from data gathering to PR creation.
  • CI-integrated tagging: generates and documents beta tag naming and registry routing.
  • Scope enforcement: operates strictly within plugins/<plugin-id>/, ensuring isolated changes.
  • PR body templates: produces a correctly formatted PR body for previews.

Quick Start

Provide the plugin-id to generate a beta-release plan and begin the guided approval workflow.

Frequently Asked Questions about prepare-beta

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

FAQPage Schema
How do I automate a beta release for a git plugin?▼

Automating a beta plugin release involves gathering git commits, classifying changes, proposing a version bump, and creating a pull request with tag instructions. This skill executes a six-phase workflow to coordinate this process and route the release via CI.

How do I generate a version bump and pull request for a beta release?▼

Generating a version bump and pull request requires analyzing recent commits within a specific plugin directory. The workflow classifies these changes, proposes the appropriate semantic version increment, and outputs a correctly formatted PR body with precise beta tag instructions.

Can I isolate beta release changes to a specific plugin directory?▼

Yes, you can isolate beta release changes because the workflow strictly enforces scope within the plugins/<plugin-id>/ directory. This ensures the version bump and pull request only reflect commits relevant to that single plugin.

What do I need to start preparing a beta plugin release?▼

To start preparing a beta plugin release, you need to provide the specific plugin-id and ensure there is access to git and the manifest.json file. This allows the workflow to gather data and begin the guided approval process.

How does CI routing work for beta plugin releases?▼

CI routing for beta plugin releases works by generating specific beta tag naming conventions documented in the pull request. These tags route the plugin correctly to the preview-registry.json during continuous integration.

Related Skills

Explore More Software Engineering Skills→
NIMBUS-MXNIMBUS-MX

release-brief

Detect release conventions, draft changelogs, and generate release commands.

Official
Intermediate
andrewendlingerandrewendlinger
5

release

Orchestrate xmris releases from preflight checks to PyPI publication.

Community
Advanced
CoooolfanCoooolfan
380

github-release

Automate GitHub release creation and format release notes via browser workflow.

Community
Basic
baekenoughbaekenough
13

omcustom-release-notes

Generate markdown release notes from git history and closed issues.

Community
Advanced