version-bumplisted

# Version Bump Before pushing changes in a marketplace project, check if any plugin files have been modified and guide the user through appropriate semver version bumps. This prevents plugins from being updated without their version reflecting the change — which matters for users who install plugins and need to know when updates are available. ## Detecting a marketplace project A marketplace project has a `.claude-plugin/marketplace.json` file at the repository root. If this file doesn't exist, this skill doesn't apply — proceed with the push normally without mentioning this skill. ## Workflow ### 1. Identify changed plugins Compare the current branch against the remote tracking branch: ```bash git diff --name-only @{upstream}...HEAD 2>/dev/null ``` If there's no upstream yet (new branch), compare against the default branch (`main` or `master`). Filter the results for paths matching `plugins/<plugin-name>/...` and extract the unique plugin names. If no plugin files changed (only root-level files like README.md), skip version bumping and proceed with the push. ### 2. Check current versions For each affected plugin, read the current version from: - `plugins/<name>/.claude-plugin/plugin.json` - `.claude-plugin/marketplace.json` Flag any version mismatches between the two files — the user should know if they've drifted out of sync. If a plugin doesn't have a `version` field in its `plugin.json`, note this and suggest adding one. ### 3. Analyze changes and suggest a