New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Bump Version

by GridTools in GridTools/gt4py

Open a PR in GitHub that bumps the GT4Py version in three files and adds a CHANGELOG entry.

BSD-3-ClauseAuto-check passedDevelopment

Install Bump Version

skills CLI
$ npx skills add GridTools/gt4py --skill bump-version -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install GridTools/gt4py bump-version --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/GridTools/gt4py.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/bump-version .claude/skills/bump-version && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
bump-version
GitHub stars
151
Token cost
~1.3k tokens
SKILL.md length
539 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
BSD-3-Clause

At a glance

Open a PR in GitHub that bumps the GT4Py version in three files and adds a CHANGELOG entry.

  • Works in 4 steps: CHANGELOG.md → Version files → verify → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers Inputs, Categorizing changes, Step 1 — CHANGELOG.md and Step 2 — Version files, plus 2 more sections
  • Calls uv

What it does

Bump Version is an agent skill from GridTools/gt4py. Open a PR in GitHub that bumps the GT4Py version in three files and adds a CHANGELOG entry.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes and Pull requests. It works with GitHub. The repository describes itself as: Python library for generating high-performance implementations of stencil kernels for weather and climate modeling from a domain-specific language (DSL). The licence is BSD-3-Clause.

When your agent uses it

  • Tasks that involve Changelog and release notes
  • Tasks that involve Pull requests

Example prompts

  • “/bump-version”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. CHANGELOG.md
  2. Version files
  3. verify
  4. branch, commit, push, PR, and release tag

What it can do on your machine

Read from SKILL.md and the folder at commit f3b3ab2. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • uv

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Bump Version loads about 1.3k tokens when it runs. Until then it costs about 26 tokens; SKILL.md has 539 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~26
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from GridTools/gt4py at commit f3b3ab2, republished under its BSD-3-Clause licence (© GridTools). 539 words, ~1,333 tokens.

Download SKILL.mdSave it as .claude/skills/bump-version/SKILL.md (or your agent's skills folder).
name
bump-version
description
Open a PR in GitHub that bumps the GT4Py version in three files and adds a CHANGELOG entry.

bump-version

Bump the GT4Py version and open a PR. For the canonical GT4Py release process, including how to publish the release tag, see docs/development/tools/release.md.

The changelog is edited manually. The remaining version edits are performed by running:

bash
./scripts/run update package-version X.Y.Z

That script updates both of the following with the same new version X.Y.Z:

  1. pyproject.toml — bump tool.versioningit.default-version.
  2. src/gt4py/__about__.py — bump on_build_version to match.

Inputs

Confirm before starting:

  • Version to bump to, e.g. 1.1.12. The project uses a CalVer-style sequence (1.1.N); the natural next value is previous + 1. Read the latest release from PyPI, not the local tree, to keep the bump idempotent. If a releasing_v* branch or an open "Releasing v*" PR already exists, use the version from that in-flight release instead of PyPI. Confirm with the user if the bump is not a simple +1.
  • Date in ISO form YYYY-MM-DD. Default to today.
  • Changelog entries grouped under General, Cartesian, and Next. Do not invent entries. Each bullet should read like user-facing release notes: describe the impact or benefit and avoid implementation details, internal class names, or backend-specific mechanics.

Categorizing changes

Use the PR title scope as the primary signal; fall back to the files touched.

ScopeSection
feat[next], fix[next], perf[next], refactor[next], test[next], docs[next], build[next], feat[next-dace], fix[next-dace], ...### Next
feat[cartesian], fix[cartesian], perf[cartesian], refactor[cartesian], test[cartesian], build[cartesian], ci[cartesian], ...### Cartesian
fix[eve], feat[eve], refactor[eve], perf[eve], ci:, build:, chore:### General

File-location tie-breakers:

  • src/gt4py/cartesian/ → ### Cartesian
  • src/gt4py/next/ → ### Next
  • src/gt4py/eve/ → ### General
  • src/gt4py/storage/ → ### General
Section contents
  • ### General — repo-wide changes: CI plumbing, eve, Python/NumPy support, top-level dependency floors, dev-infra, coding-agents harness.
  • ### Cartesian — user-visible gt4py.cartesian changes: stencils, backends, frontend syntax, code generation, caching, cartesian dependency bumps, and user-visible build/CI changes for cartesian.
  • ### Next — always exactly:
    ### Next

See commit history.
    Review next PRs only to ensure none belong in General or Cartesian; do not write bullets for them.

Exclude entirely when purely internal with no user-visible effect:

  • Pure refactoring with no behaviour change.
  • Pure test code additions/fixes.
  • Pure docs/chore with no user-facing impact.

When a PR mixes categories, file it under its primary user-visible effect.

Show full SKILL.md (214 more words)Show less

Step 1 — CHANGELOG.md

Insert a new block immediately after the two-line file header and before the previous release:

markdown
## [X.Y.Z] - YYYY-MM-DD

### General

- <bullet, if any>

### Cartesian

- <bullet, one per change>
- <another change>

### Next

See commit history.

Rules:

  • Headings appear in this order: General, Cartesian, Next.
  • General is optional; omit it if empty.
  • Next is always the fixed placeholder above.
  • Use present-tense imperative-ish phrasing for bullets.
  • Keep bullets user-focused, not implementation-focused.
  • Do not include PR or issue numbers in bullets; the commit/PR history already links them.
  • Blank lines separate the header, each section, and the previous release.

Step 2 — Version files

Run the helper script to bump the fallback version in both pyproject.toml and src/gt4py/__about__.py:

bash
./scripts/run update package-version X.Y.Z

This preserves the required +unknown.version.details local part.

Step 3 — verify

Confirm all three occurrences use the same X.Y.Z:

  • CHANGELOG.md: ## [X.Y.Z] - ...
  • pyproject.toml: default-version = "X.Y.Z+unknown.version.details"
  • src/gt4py/__about__.py: on_build_version: Final = "X.Y.Z+unknown.version.details"

Step 4 — branch, commit, push, PR, and release tag

  • Branch: releasing_vX.Y.Z
  • Commit / PR title: Releasing vX.Y.Z (note the v prefix here only)
  • PR body: Bump version to X.Y.Z and update CHANGELOG. (optional)
  • Target: upstream main (GridTools/gt4py:main)

If releasing_vX.Y.Z already exists, commit on that branch and push; do not open a duplicate PR.

Stage the changed files, then run:

uv run pre-commit run

Do not run the full -a suite or the test suites for a pure metadata bump.

After the PR is merged, publish the GitHub release and tag vX.Y.Z following the instructions in docs/development/tools/release.md.

© GridTools, BSD-3-Clause. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/bump-version of GridTools/gt4py.

Open the folder on GitHubat commit f3b3ab2

Compare with similar skills

Bump Version next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Bump Version compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Bump Version this skillGridTools/gt4py151—~1.3kAutomated safety check: PassBSD-3-Clause
Verdaccio Pull Request Workflowverdaccio/verdaccio18k—~1.9kAutomated safety check: PassMIT
Plannotator Release Preparationbacknotprop/plannotator9.3k—~4.6kAutomated safety check: PassApache-2.0
Ansible Pull Request Reviewansible/ansible71k—~570Automated safety check: PassGPL-3.0
Plane Release Notes Generatormakeplane/plane61k—~2.5kAutomated safety check: PassAGPL-3.0
Pair GitHub PRNVIDIA/Personal-AI-Router1.6k—~1.3kAutomated safety check: PassApache-2.0

Similar skills

  • Verdaccio Pull Request Workflow

    verdaccio/verdaccio

    Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.

    18k GitHub stars~1.9k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Plannotator Release Preparation

    backnotprop/plannotator

    Drafts Plannotator release notes with full contributor credit, bumps versions in dependency order, builds, and starts the tag-driven release pipeline, in four reviewed phases.

    9.3k GitHub stars~4.6k tokensUpdated today
    DevelopmentAuto-check passed

  • Ansible Pull Request Review

    ansible/ansible

    Reviews an Ansible pull request by number, following the steps in the project's CLAUDE.md, with early checks for changelog fragments and tests.

    71k GitHub stars~570 tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Plane Release Notes Generator

    makeplane/plane

    Builds categorized release notes for a Plane release pull request from its commits and writes them into the PR description, for both the plane-cloud and plane-ee repos.

    61k GitHub stars~2.5k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Pair GitHub PR

    NVIDIA/Personal-AI-Router

    Official

    Fills GitHub pull request descriptions with the required PAIR pair-release-intent:v1 block so the release-intent check passes.

    1.6k GitHub stars~1.3k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Handsontable Changelog Entry

    handsontable/handsontable

    Decides whether a code change needs a changelog entry and creates the JSON file in .changelogs with the right type, framework and user-facing title.

    22k GitHub stars~1.6k tokensUpdated yesterday
    DevelopmentAuto-check passed

Works with

Categories

Questions about Bump Version

What does Bump Version do?

Open a PR in GitHub that bumps the GT4Py version in three files and adds a CHANGELOG entry. Bump Version is an agent skill from GridTools/gt4py. Open a PR in GitHub that bumps the GT4Py version in three files and adds a CHANGELOG entry.

When should I use Bump Version?

Bump Version fits situations like: tasks that involve Changelog and release notes; tasks that involve Pull requests.

How do I install Bump Version in Claude Code?

Run `npx skills add GridTools/gt4py --skill bump-version -a claude-code`. Or copy the skill folder (.agents/skills/bump-version in GridTools/gt4py) into .claude/skills/bump-version in your project. Claude Code loads it when a task matches its description.

How do I install Bump Version in Codex?

Run `npx skills add GridTools/gt4py --skill bump-version -a codex`. Or copy the skill folder (.agents/skills/bump-version in GridTools/gt4py) into .agents/skills/bump-version in your project. Codex loads it when a task matches its description.

Can I use Bump Version in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add GridTools/gt4py --skill bump-version -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/bump-version, .gemini/skills/bump-version, .github/skills/bump-version and .opencode/skills/bump-version in your project.

What does Bump Version need to run?

Going by SKILL.md and its folder, Bump Version needs the command-line tools its instructions call (uv).

Does Bump Version access the network?

SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Bump Version safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Bump Version use?

Bump Version is published under the BSD-3-Clause licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Bump Version use?

About 1.3k tokens (SKILL.md is roughly 5.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Bump Version?

Skills that share tags, products or a category with Bump Version: Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Plannotator Release Preparation (backnotprop/plannotator, 9.3k stars), Ansible Pull Request Review (ansible/ansible, 71k stars) and Plane Release Notes Generator (makeplane/plane, 61k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bump Version?

GridTools (a GitHub organization) maintains it in GridTools/gt4py, which has 151 GitHub stars. The repository was last updated on October 9, 2026.

Source: GridTools/gt4py on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.