Skip to content
Skills Library
Programming · Automation

bump-version

/bump-version

Bump the membrowse package version (pyproject.toml and the Claude plugin manifests), open a PR, wait for CI to pass and squash-merge it. Use when the user asks to bump the version, cut a patch/minor/major release version, or run /bump-version. Accepts an optional argument - "patch" (default), "minor", "major", or an explicit version like 1.3.0.

Licence
GPL-3.0
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

GPL-3.0, otwarta.

What it does and when to use it

Bump the membrowse package version (pyproject.toml and the Claude plugin manifests), open a PR, wait for CI to pass and squash-merge it. Use when the user asks to bump the version, cut a patch/minor/major release version, or run /bump-version. Accepts an optional argument - "patch" (default), "minor", "major", or an explicit version like 1.3.0.

Triggers from the description

patchminormajor
Original author description

Bump the membrowse package version (pyproject.toml and the Claude plugin manifests), open a PR, wait for CI to pass and squash-merge it. Use when the user asks to bump the version, cut a patch/minor/major release version, or run /bump-version. Accepts an optional argument - "patch" (default), "minor", "major", or an explicit version like 1.3.0.

How it works

  1. 1. Preconditions — stop if any fails
  2. 2. Compute the new version
  3. 3. Branch, commit, push, PR
  4. 4. Wait for checks
  5. 5. Merge and clean up
Original SKILL.md headings · 60 lines, 430 words
SKILL.md preview
---
name: bump-version
description: Bump the membrowse package version (pyproject.toml and the Claude plugin manifests), open a PR, wait for CI to pass and squash-merge it. Use when the user asks to bump the version, cut a patch/minor/major release version, or run /bump-version. Accepts an optional argument - "patch" (default), "minor", "major", or an explicit version like 1.3.0.
---

# Bump version

Bumps the version, opens a PR, waits for its checks and merges it. Argument: `patch` (default), `minor`, `major`, or an explicit `X.Y.Z`.

## 1. Preconditions — stop if any fails

```bash
git rev-parse --abbrev-ref HEAD          # must print: main
git fetch origin main
git status --porcelain --untracked-files=no   # must be empty (untracked files are fine)
git rev-list --count HEAD..origin/main   # must be 0; if not, `git pull --ff-only` first
git rev-list --count origin/main..HEAD   # must be 0 (no unpushed local commits on main)
```

If the branch is not `main`, stop and tell the user — do not switch branches for them. If tracked files are modified, stop and report them.

## 2. Compute the new version

Read the current version from `pyproject.toml` (`version = "X.Y.Z"` under `[project]`). Apply the argument:
- `patch` → `X.Y.(Z+1)`; `minor` → `X.(Y+1).0`; `major` → `(X+1).0.0`; explicit → use as given (must be greater than current).

The version appears in exactly these three places — update all of them and nothing else:
- `pyproject.toml` — `version = "…"`
- `.claude-plugin/plugin.json` — `"version": "…"`
- `.claude-plugin/marketplace.json` — `"version": "…"` of the plugin entry

Verify with `grep -rn '"version"\|^version' pyproject.toml .claude-plugin/` that all three show the new version. Do not touch version mentions in tests or docs (those are historical references).

## 3. Branch, commit, push, PR

```bash
git checkout -b bump-vNEW
git add pyproject.toml .claude-plugin/plugin.json .claude-plugin/marketplace.json
git commit -m "bump vNEW"
git push -u origin bump-vNEW
gh pr create --base main --head bump-vNEW --title "bump vNEW" \
  --body "Bump version to NEW in pyproject.toml and the Claude plugin manifests."
```

No `Co-Authored-By` trailers or "Generated with Claude Code" lines in the commit or PR body. If the user gave a reason for the release (e.g. "patch for #191"), add it as the first line of the PR body.

## 4. Wait for checks

```bash
gh pr checks bump-vNEW --watch --fail-fast
```

Run it in the background or with a long timeout (CI takes several minutes). If checks have not registered yet, `gh pr checks` may report none — wait ~30 s and retry. If any check fails, stop: report the failing check and its log (`gh run view <run-id> --log-failed`), and leave the PR open. Do not merge.

## 5. Merge and clean up

```bash
gh pr merge bump-vNEW --squash --delete-branch
git checkout main
git pull --ff-only
```

Report the merged PR URL and the new version. Merging does not publish to PyPI — publishing runs on a GitHub release (`.github/workflows/publish-to-pypi.yml`). Mention that, but do not create the release unless the user asks.

Versions

RepositoryScoreLicence
This page · membrowse/membrowse-action100GPL-3.0
lorem-dev/duolog100Apache-2.0
waldekmastykarz/vally-claudecodecli100MIT
cassandragargoyle/skill-source-trust-assessment100MIT
iofficeai/aionui100Apache-2.0
ChandraChaan/flutter-release-kit100MIT
sd0xdev/sd0x-harness100MIT
hyhmrright/logic-lens100MIT
quantumbfs/sci-brain100MIT

Database snapshot: 13.11.2026 · package version 00f05efb54de (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100version
    This skill should be used when the user wants to bump versions, create releases, or tag versions. Triggers include: "bump version", "bump the version", "version bump", "release version", "tag a release", "create release", "major/minor/patch bump", "update version", "new…
  • 100version-bump
    ACTIVATE before every `gh pr create` / `gh pr edit` in the claude-marketplace repo, and before any commit that touches files under plugins/. ACTIVATE for 'bump version', 'bump les versions', 'release plugin', 'version bump', 'semver', 'mets à jour les versions'. Classifies the…
  • 100new-release
    Prepare a Graphmem release or version bump. Use whenever the user asks to release, cut a version, bump a patch/minor/major version, update the changelog, or synchronize Graphmem, OpenCode/pi, Claude Code, and Codex plugin versions.
  • 100version-release
    Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.
  • 100version-release
    Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.
  • 100release
    Cut a new release of ra-mcp. Determines the next version from the commit history since the last tag, bumps pyproject.toml, commits, tags, and pushes. Use when: "make a release", "cut a release", "release", "bump version", "tag a new version", "publish a new version".

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.