Skip to content
Skills Library
DevOps & cloud · Automation

bump-version

/bump-version

Use when asked to bump the version, prepare or create a release, update the version number, or determine a semantic version increment from recent commits.

Licence
MIT
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
1
Deprecation

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

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when asked to bump the version, prepare or create a release, update the version number, or determine a semantic version increment from recent commits.

Original author description

Use when asked to bump the version, prepare or create a release, update the version number, or determine a semantic version increment from recent commits.

How it works

  1. Workflow
Original SKILL.md headings · 74 lines, 322 words
SKILL.md preview
---
name: bump-version
description: 'Use when asked to bump the version, prepare or create a release, update the version number, or determine a semantic version increment from recent commits.'
---

# Bump Version

Analyze unreleased commits, recommend a semantic version bump, and apply it with
`npm version` only after the user confirms.

## Workflow

Follow these steps in order.

### 1. Identify the release range

Run `git tag --list 'v*' --sort=-v:refname | head -1`. If a tag exists, inspect
`git log <latest-tag>..HEAD --oneline`. Otherwise, inspect `git log --oneline` and
treat this as the initial release.

Stop if there are no unreleased commits.

### 2. Recommend the bump

Choose the highest applicable level:

- **major**: a breaking change, including `BREAKING CHANGE`, `BREAKING:`, or `!`
  after a conventional commit type
- **minor**: new functionality, including `feat:` or `feat(scope):`
- **patch**: fixes, documentation, dependencies, maintenance, refactoring, tests,
  CI, or performance improvements

Read the current version from `package.json` and calculate the proposed version.

### 3. Confirm with the user

**STOP. Do not modify files, commit, or tag without confirmation.**

Show the unreleased commits, recommended bump with reasoning, and current and
proposed versions. Ask the user to confirm or choose another bump type.

### 4. Update the changelog

After confirmation, read `CHANGELOG.md` if it exists and preserve its style. If it
does not exist, create it with a `# Changelog` heading.

Add the new release below the heading using today's date. Include only applicable
sections from **Features**, **Bug fixes**, and **Maintenance**. Describe user-facing
changes rather than copying commit messages. Skip internal changes unless they
affect users.

When a previous tag exists, link the version heading to:

`https://github.com/waldekmastykarz/vally-claudecodecli/compare/vPREVIOUS...vNEW`

Stage `CHANGELOG.md`.

### 5. Apply the version bump

Commit the changelog, then run `npm version`:

```sh
git commit -m "docs: update changelog for vX.Y.Z"
npm version <patch|minor|major>
```

`npm version` requires a clean working tree. Do not discard unrelated changes to
make it clean; stop and explain what must be committed first.

### 6. Publish

Remind the user to push the commits and tag:

```sh
git push && git push --tags
```

The tag triggers `.github/workflows/publish.yml`, which publishes to npm.

Versions

RepositoryScoreLicence
This page · waldekmastykarz/vally-claudecodecli100MIT
membrowse/membrowse-action100GPL-3.0
lorem-dev/duolog100Apache-2.0
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 11cc93c954f0 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 1 · ranking

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

Similar skills

  • 100version-bump
    Increment app version numbers. Use when user asks to bump version, increment version, or prepare a release.
  • 95prepare_release
    Prepare a release by analyzing all changes since the last git tag, updating CHANGELOG.md with categorized entries, inferring the next semantic version, and auditing all documentation for staleness or missing content. Triggered by requests like "prepare release", "bump version",…
  • 86release
    Cut a release of slinger. Use when the user says "release", "cut a release", "ship X.Y.Z", or "bump the version".
  • 100release
    Create a release branch from dev with version bumps and changelog. Use when the user wants to prepare a new release, bump a version, or cut a release. Triggers on phrases like "release 17.1.2", "cut a release", "prepare a release", "version bump", or just "/release".
  • 100release
    Prepare and publish a new cryptobot-python release. Use when the user asks to cut a release, bump the package version, update HISTORY.md, create a git tag, or create a GitHub release.
  • 100release
    Generate changelog from commits, bump version, create GitHub release, publish to npm. Use when user wants to release, publish, or ship 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.