New: 97,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

Iflow Version Bump

by jepegit in jepegit/cellpy

Bump the project version following the project's release strategy: static pyproject versions via uv, or tag-derived versions via a planned git tag.

MITAuto-check passedDevelopment

Install Iflow Version Bump

skills CLI
$ npx skills add jepegit/cellpy --skill iflow-version-bump -a claude-code

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

GitHub CLI
$ gh skill install jepegit/cellpy iflow-version-bump --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/jepegit/cellpy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/iflow-version-bump .claude/skills/iflow-version-bump && 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
iflow-version-bump
GitHub stars
109
Token cost
~1.6k tokens
SKILL.md length
821 words
Files
1
Skills in repo
31
Repo updated
First seen
Licence
MIT

At a glance

Bump the project version following the project's release strategy: static pyproject versions via uv, or tag-derived versions via a planned git tag.

  • Works in 3 steps: .issueflows/04-designs-and-guides/this-pr… → Detect from pyproject.toml → Neither (no pyproject.toml, or no…
  • Tasks that involve Git workflow
  • SKILL.md covers Resolve the release strategy…, Bump levels (both strategies), Choosing the level and Strategy: static version (uv), plus 2 more sections
  • Calls uv, git and gh

What it does

Iflow Version Bump is an agent skill from jepegit/cellpy. Bump the project version following the project's release strategy: static pyproject versions via uv, or tag-derived versions via a planned git tag.

Its SKILL.md is about 1.6k 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 Git workflow. It works with Git. The repository describes itself as: extract and tweak data from electrochemical tests of cells. The licence is MIT.

When your agent uses it

  • Tasks that involve Git workflow

Example prompts

  • “/iflow-version-bump”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. .issueflows/04-designs-and-guides/this-project.md — if its "Release & version bump" section is filled in, follow it verbatim. It is the…
  2. Detect from pyproject.toml
  3. Neither (no pyproject.toml, or no version at all) → skip the bump, explain why, and continue the rest of the flow (for example…

What it can do on your machine

Read from SKILL.md and the folder at commit ff2c665. 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
    • git
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use uv, git and gh, 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

Iflow Version Bump loads about 1.6k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 821 words of instructions outside code blocks.

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

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 jepegit/cellpy at commit ff2c665, republished under its MIT licence (© jepegit). 821 words, ~1,620 tokens.

Download SKILL.mdSave it as .claude/skills/iflow-version-bump/SKILL.md (or your agent's skills folder).
name
iflow-version-bump
description
Bump the project version following the project's release strategy: static pyproject versions via uv, or tag-derived versions via a planned git tag.
disable-model-invocation
true
issue-flow-version
0.4.2a4

issue-flow — version bump

Use this skill to bump the project version before landing work (often invoked from /iflow-close) — either at a specific level, or with the default rule below when none is given. What "bump" means depends on the release strategy, so resolve that first.

MODEL & EXECUTION DIRECTIVE

Profile: economy — Prioritize speed and token economy over deep reasoning.

In Cursor: use Auto or a fast model before invoking this step.

Keep scope tight to what this step requires.

CLI fast path (optional). If the issue-flow CLI is on PATH, run issue-flow agent version-plan [--bump <level>] --json. It detects the strategy from pyproject.toml, reads the latest tag, does the PEP 440 next-version arithmetic, and returns the exact commands — read-only, it never edits files or creates tags. The this-project.md release section still wins over its detection: when the payload says brief_release_section: "filled", read the section and follow it. If the CLI is missing or errors, fall back to the manual steps below.

Resolve the release strategy first

In order — stop at the first that answers:

  1. .issueflows/04-designs-and-guides/this-project.md — if its "Release & version bump" section is filled in, follow it verbatim. It is the project's own documentation and beats every default below.
  2. Detect from pyproject.toml:
    • dynamic = ["version"] under [project], together with a tag-driven backend ([tool.setuptools_scm], hatch-vcs in the build requires, versioningit, or similar) → git-tag derived strategy.
    • a static version = "..." under [project] → static version (uv) strategy.
  3. Neither (no pyproject.toml, or no version at all) → skip the bump, explain why, and continue the rest of the flow (for example /iflow-close) without failing.

Record what you learn (self-healing). When the strategy came from detection or from the user explaining it — i.e. not from this-project.md — add or fill in the "Release & version bump" section of .issueflows/04-designs-and-guides/this-project.md with a short description of the strategy and the exact commands, so no future session has to rediscover it. The brief is user-owned and never overwritten by issue-flow update, so the note is durable.

Bump levels (both strategies)

Every level below is allowed; the same table drives both strategies (examples from 0.4.1a4):

LevelEffect
major1.0.0
minor0.5.0
patch0.4.2
stable0.4.1 — drop the pre-release/dev segment
alpha0.4.1a5 — next alpha pre-release
beta0.4.1b1 — promote/advance to beta
rc0.4.1rc1 — promote/advance to release candidate
post0.4.1a4.post1 — post-release
devdev release — must be paired with another component

Choosing the level

  1. The user named a level (patch, minor, major, stable, alpha, beta, rc, post, dev) → use exactly that.
  2. The user asked to bump/release but gave no level → apply the pre-release-aware default, based on the current version (static field, or latest tag):
    • current is an alpha (aN) → next alpha
    • current is a beta (bN) → next beta
    • current is a release candidate (rcN) → next rc
    • current is a dev release (.devN) → advance dev paired with the component being advanced (default patch)
    • current is a stable release (no pre-release segment) → patch
  3. Free-text intent (e.g. "bugfix release", "promote to beta") → map to the matching level (bugfix → patch, "to beta" → beta); if genuinely ambiguous, ask once rather than guessing major.
Show full SKILL.md (317 more words)Show less

Strategy: static version (uv)

For a Python + uv project whose pyproject.toml has a [project] version field.

  1. Run from the project root (the directory that contains pyproject.toml).
  2. Use only uv with --bump <level>:
bash
uv version --bump patch     # 0.4.1a4 -> 0.4.2
uv version --bump alpha     # 0.4.1a4 -> 0.4.1a5
uv version --bump minor --bump alpha   # combine: 0.4.1a4 -> 0.5.0a1

Tip: preview without writing using uv version --dry-run --bump <level> --short.

  1. Afterwards: confirm the new version in pyproject.toml (or the uv output). When committing later, stage pyproject.toml; if uv.lock changed as well, stage it too — otherwise do not assume it changed.

Strategy: git-tag derived

For projects whose built version comes from the latest git tag (setuptools-scm, hatch-vcs, versioningit, …). Here bumping means planning a tag, and the tag is created after the PR merges — never before.

  1. Never edit a version into pyproject.toml — the backend derives it.
  2. Find the current version: latest tag via git describe --tags --abbrev=0 (or git tag --sort=-v:refname and take the first). Keep the project's existing tag style (e.g. a leading v).
  3. Compute the planned next version from the level table above (e.g. latest v1.0.4a2 + alpha → planned v1.0.4a3).
  4. Do not create the tag during /iflow-close. In a squash-merge world the issue-branch commit never lands on the default branch, so a pre-merge tag would point at an orphan. Instead:
    • report the planned tag in the close output and record it in the issue's status file,
    • let HISTORY.md promotion use the planned version,
    • create the tag after the merge, standing on the updated default branch (this is offered by /iflow-cleanup, or happens right after the post-merge pull in a yolo close):
bash
git tag v1.0.4a3
git push origin v1.0.4a3
# or, to also cut a GitHub release:
gh release create v1.0.4a3 --generate-notes

Constraints

  • Do not substitute pip or hand-edit versions unless the strategy's own tool fails and the user agrees to an alternative.
  • Never silently jump release channels: don't promote an alpha to stable (or bump major/minor) just because no level was given — the default keeps you on the current pre-release channel.
  • Tag-derived projects: never tag an issue-branch commit; the tag is created on the merged default branch only.

© jepegit, MIT. 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 .cursor/skills/iflow-version-bump of jepegit/cellpy.

Open the folder on GitHubat commit ff2c665

Compare with similar skills

Iflow Version Bump 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.

Iflow Version Bump compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Iflow Version Bump this skilljepegit/cellpy109—~1.6kAutomated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Code Design Rationale Investigatorcursor/plugins10k9 repos~2.6kAutomated safety check: PassNone
Contributor-First PR MergeHKUDS/OpenHarness16k1 repos~847Automated safety check: PassMIT
Migrate Internal Package into GhostTryGhost/Ghost55k—~3.8kAutomated safety check: PassMIT
Create Pull Requestcline/cline70k1 repos~1.6kAutomated safety check: PassApache-2.0

Similar skills

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Code Design Rationale Investigator

    cursor/plugins

    Official

    Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.

    10k GitHub starsUsed in 9 repos~2.6k tokens
    DevelopmentAuto-check passed

  • Contributor-First PR Merge

    HKUDS/OpenHarness

    Merges external GitHub pull requests while keeping the original author credited, and fixes conflicts after the merge instead of rewriting the contribution.

    16k GitHub starsUsed in 1 repo~847 tokens
    DevelopmentAuto-check passed

  • Migrate Internal Package into Ghost

    TryGhost/Ghost

    Moves a package from another TryGhost repository into Ghost as an internal workspace package while keeping its Git history, with checkpoints for the steps that need an administrator.

    55k GitHub stars~3.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Create Pull Request

    cline/cline

    Opens a GitHub pull request from your current branch with the gh CLI, after reviewing the commits and diff and gathering the details the PR needs.

    70k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

  • Git Merge Conflict Resolver

    tailcallhq/forgecode

    Resolves Git merge conflicts with a plan-first workflow that keeps both sides' intent, regenerates lock files and backs up deleted-but-modified files.

    7.6k GitHub starsUsed in 1 repo~4.5k tokens
    DevelopmentAuto-check passed

More from jepegit/cellpy

All 31 skills in this repo

  • Gh CI

    jepegit/cellpy

    Use GitHub CLI to snapshot or wait on CI for a pull request or workflow run.

    109 GitHub stars~667 tokensUpdated yesterday
    Auto-check passed

  • Caveman

    jepegit/cellpy

    Respond in a terse "smart caveman" style that keeps all technical substance but drops filler, articles, and pleasantries.

    109 GitHub stars~725 tokensUpdated yesterday
    Auto-check passed

  • Grill Me

    jepegit/cellpy

    Interview the user relentlessly about a plan or design until every branch of the decision tree is resolved, then feed the conclusions into the issue plan.

    109 GitHub stars~676 tokensUpdated yesterday
    Auto-check passed

  • Iflow Archive

    jepegit/cellpy

    Condense old solved issue groups into one dated summary file, then delete the originals.

    109 GitHub stars~1.3k tokensUpdated yesterday
    Auto-check passed

  • Iflow Capture

    jepegit/cellpy

    Capture a GitHub issue locally as issue<numberoriginal.md and archive other current issues by done status.

    109 GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

  • Iflow Comments

    jepegit/cellpy

    Triage a GitHub issue's comment thread into the curated, bucketed summary section of issue<Noriginal.md.

    109 GitHub stars~1.4k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Iflow Version Bump

What does Iflow Version Bump do?

Bump the project version following the project's release strategy: static pyproject versions via uv, or tag-derived versions via a planned git tag. Iflow Version Bump is an agent skill from jepegit/cellpy. Bump the project version following the project's release strategy: static pyproject versions via uv, or tag-derived versions via a planned git tag.

When should I use Iflow Version Bump?

Iflow Version Bump fits situations like: tasks that involve Git workflow.

How do I install Iflow Version Bump in Claude Code?

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

How do I install Iflow Version Bump in Codex?

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

Can I use Iflow Version Bump 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 jepegit/cellpy --skill iflow-version-bump -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/iflow-version-bump, .gemini/skills/iflow-version-bump, .github/skills/iflow-version-bump and .opencode/skills/iflow-version-bump in your project.

What does Iflow Version Bump need to run?

Going by SKILL.md and its folder, Iflow Version Bump needs the command-line tools its instructions call (uv, git and gh). Our summary lists: Python 3.

Does Iflow Version Bump access the network?

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

Is Iflow Version Bump 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 Iflow Version Bump use?

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

How many tokens does Iflow Version Bump use?

About 1.6k tokens (SKILL.md is roughly 6.5k 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 Iflow Version Bump?

Skills that share tags, products or a category with Iflow Version Bump: Finishing a Development Branch (obra/superpowers, 296k stars), Code Design Rationale Investigator (cursor/plugins, 10k stars), Contributor-First PR Merge (HKUDS/OpenHarness, 16k stars) and Migrate Internal Package into Ghost (TryGhost/Ghost, 55k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Iflow Version Bump?

jepegit (a GitHub user) maintains it in jepegit/cellpy, which has 109 GitHub stars. The repository holds 31 skills in this directory. The repository was last updated on October 6, 2026.

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