release

# Release Bump version, write changelog, commit, and push for a single plugin in the monorepo. The changelog entry is critical because the upgrade skill (`skills/hermit-evolve/SKILL.md`) reads it to know what to tell hermits during `/claude-code-hermit:hermit-evolve`. ## Usage `/release <plugin-slug>` — release the plugin at `plugins/<plugin-slug>/`. Examples: - `/release claude-code-hermit` — release the core plugin - `/release claude-code-dev-hermit` — release the dev hermit - `/release claude-code-homeassistant-hermit` — release the HA hermit - `/release laravel-forge-hermit` — release the Laravel Forge hermit If invoked without a slug, list all `plugins/<name>/` directories that contain `.claude-plugin/plugin.json` and ask the operator which one via AskUserQuestion before proceeding. ## Steps ### 0. Identify target plugin Resolve the plugin slug: - If the user passed `<slug>` as argument, use that. - Otherwise, glob `plugins/*/.claude-plugin/plugin.json`, collect the directory names, and ask via AskUserQuestion: "Which plugin to release?" with one option per slug. Validate `plugins/<slug>/.claude-plugin/plugin.json` exists. If it does not, abort: `Plugin 'plugins/<slug>/' not found.` Suggest the available slugs. Throughout the rest of this skill, `$PLUGIN_DIR` refers to `plugins/<slug>/`. ### 1. Pre-release validation Run before anything else. Abort the release if any step fails. 1. **Run the native plugin validator (CLI form):** ```bash claude plugin v...