releaselisted

# Release a plugin Use this workflow only after an explicit release request. - Claude Code invocation: `/release <plugin-name> [version|major|minor|patch]` - Codex invocation: `$release <plugin-name> [version|major|minor|patch]` Read the plugin name and optional version from the current request: - First argument: plugin name, required, for example `ufil`. - Second argument: exact `X.Y.Z`, `major`, `minor`, or `patch`. - When the second argument is omitted, bump the patch version. - If the plugin name is missing, stop and list available plugins from `.claude-plugin/marketplace.json`. ## Outcome 1. Validate the plugin and repository release state. 2. Determine the next version. 3. Keep Claude and Codex plugin manifests synchronized. 4. Commit the version bump. 5. Create and push an annotated tag. 6. Generate release notes. 7. Create the GitHub release. ## 1. Pre-flight checks Run these independent checks in parallel when the client supports it: ```bash git status --porcelain git branch --show-current git fetch --tags origin git remote get-url origin ``` Require all of the following: - Working tree is clean. - Current branch is `main`. - `plugins/<plugin>/.claude-plugin/plugin.json` exists. - The plugin appears in `.claude-plugin/marketplace.json`. - The remote repository is `ghozimahdi/gm-aiagent-plugins`. If the plugin also has `plugins/<plugin>/.codex-plugin/plugin.json`, require its base semantic version to match the Claude manifest before continuing. Ignore a