Clubhouse-Workshop: Skill for Claude Code

Prepare a Plugin Beta Release

This skill prepares a beta release for a single Workshop plugin using a 6-phase flow. The user provides the plugin ID as $ARGUMENTS. If omitted, list available plugins and ask.

Scope: All work is filtered to plugins/<plugin-id>/ — only commits touching that directory are considered.

---

Phase 1: Gather Data

# Ensure main is up to date
git checkout main && git pull origin main

# Read current version from manifest
cat plugins/<plugin-id>/manifest.json | grep '"version"'

# Find existing tags for this plugin
git tag --list '<plugin-id>-v*' --sort=-v:refname | head -10

# Determine last stable tag (no -beta in name) and last beta tag
LAST_STABLE=$(git tag --list '<plugin-id>-v*' --sort=-v:refname | grep -v '\-beta\.' | head -1)
LAST_BETA=$(git tag --list '<plugin-id>-v*-beta.*' --sort=-v:refname | head -1)

# Collect commits since last tag (stable or beta, whichever is newer)
# Use the newer of the two as the base
git log <last-tag>..HEAD --oneline --no-merges -- plugins/<plugin-id>/

If no previous tags exist for this plugin, collect all commits touching plugins/<plugin-id>/.

Determine beta increment: if LAST_BETA exists and is newer than LAST_STABLE, increment its beta number. Otherwise, start at -beta.1.

---

Phase 2: Classify Commits

Classify each commit using first-match-wins:

1. Feature — feat: prefix, or clearly new user-visible functionality
2. Bug Fix — fix: prefix, or user-visible bug correction
3. Internal — perf: prefix, optimizations, performance improvements
4. Non-User — chore:, ci:, test:, docs:, build:, refactor:

Skip version bump commits entirely (chore: bump version to ...).

---

Phase 3: Coalesce

• A Feature absorbs closely related fixes (show final state only)
• Multiple fixes in the same area → one entry
• Keep distinct items separate
• Drop all Non-User items completely — they never appear in release notes or PR body
• Internal items appear only as "Improvements" in the PR body (not in the title)