version-bumplisted

Automate version bumping across an npm monorepo (npm workspaces), promote CHANGELOG entries, and open a PR with auto-merge enabled. > **Scope note (2026-07-23):** in release-please repos (the default), release-please owns version bumping and changelog promotion via its release PR — do not run this skill there. It remains for repos without release-please configured. ## Prerequisites - Active git repo with root `package.json` and npm workspaces in `packages/*/package.json` - `CHANGELOG.md` exists with `[Unreleased]` section - Git repo is clean (no unstaged changes) - GitHub CLI (`gh`) is installed and authenticated - Current branch is `main` (or `master`) ## Workflow 1. **Validate version argument**: Ensure `NEXT_VERSION` matches semantic versioning (e.g., `2.7.0`) 2. **Check git state**: Fail if uncommitted changes exist or if `NEXT_VERSION` is already tagged 3. **Bump versions**: Update root `package.json` and all `packages/*/package.json` to `NEXT_VERSION` 4. **Promote CHANGELOG**: Move `[Unreleased]` section header to `[NEXT_VERSION] - YYYY-MM-DD` (today's date) 5. **Create branch**: `chore/bump-NEXT_VERSION` 6. **Commit**: Message = `chore: bump version to NEXT_VERSION` 7. **Push**: Push the branch to origin 8. **Open PR**: Use `gh pr create --auto-merge` with standard description 9. **Verify**: Confirm tag does not exist before proceeding; never force-push ## Safety rules - **No force-push**: Uses `git push origin <branch>` only - **Tag conflict check**: Stop if gi