agentleFS
lorem-devlorem-dev/duolog/.claude/skills/bump-version/SKILL.md

bump-version

Skill4 starsChanged 16 days agoApache-2.0View on GitHub

Use when the user asks to bump, set or raise the duolog version, or to

43 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use oss-pr, pr-automation and 7 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • CES-LtdSkill

    oss-pr

    Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.

    Also in 3 projects that use this

  • CES-LtdSkill

    pr-automation

    PR Automation Orchestrator: poll open PRs, check CI, run review, fix, and merge eligible PRs. Use when: (1) Invoked by daemon via scripts/pr-automation.sh, (2) User says "/pr-automation".

    Also in 3 projects that use this

  • volovelySkill

    pr-fix

    This skill should be used when the user asks to "fix PR comments", "address PR feedback", "resolve PR comments", provides a GitHub PR URL with intent to fix, or says "pr-fix". It reads all review comments on a PR, decides which need code fixes vs. replies, makes the fixes, and posts replies — all with explicit user approval before any GitHub action.

    Also in 3 projects that use this

  • lbednerSkill

    i18n

    Use when a code or template change introduces a new translation message key, in either the framework CLI (aegis/i18n/locales/) or a generated project's CLI (the app/i18n/locales/ template tree). Covers adding the real English string, stubbing the same key into every other locale for parity, and the separate translation PR that later replaces placeholders with reviewed native text.

    Also in 4 projects that use this

  • AnthropicSkill

    architecture

    Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.

    Also in 4 projects that use this

  • NVIDIASkill

    testing

    Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.

    Also in 5 projects that use this

  • +2 more from CES-Ltd

The file

We split this skill into the rules it gives an agent

9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Write files, comments and reports in English, ASCII only.

    line 21
  2. Distinctive:

    Use simple English: short sentences, common words, simple grammar.

    line 22
  3. Very specific:

    Run uv --version. If it fails, stop and ask the user to install uv: https://docs.astral.sh/uv/getting-started/installation/

    line 31
  4. Distinctive:

    Run git status --short. If it prints anything, stop and ask the user to commit or stash first.

    line 36
  5. Very specific:

    If $version is empty, ask: "Which version?

    line 41
  6. Very specific:

    Read ## Development in CHANGES.md.

    line 43
  7. Distinctive:

    Check every place against the new version:

    line 57
  8. Distinctive:

    Read git diff. Only the version and the new heading may change.

    line 63
  9. Very specific:

    Commit, if the user asked for a commit: release: $version.

    line 66

“Common” is measured: kept by at least 6 in 10 of the 40 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Bump the version

Arguments

  • $version - the new version, such as 1.2.3 or 1.2.3-rc.1, with no v. When it is missing, ask for it in step 1.

Communication

  • Reply in the language the user writes in.
  • Write files, comments and reports in English, ASCII only.
  • Use simple English: short sentences, common words, simple grammar.

Models

  • The current model does all of it. The script writes the files, so a small model is enough.

Before you start

  • Run uv --version. If it fails, stop and ask the user to install uv: https://docs.astral.sh/uv/getting-started/installation/
  • A sandbox can stop uv from writing its cache. If a later uv run reports that, set the variable UV_CACHE_DIR to .cache/uv, which git ignores, and run it again. Do not call Python directly, and do not edit the files by hand instead.
  • Run git status --short. If it prints anything, stop and ask the user to commit or stash first. The bump must be an isolated diff.

Steps

  1. If $version is empty, ask: "Which version? Example: 1.2.3"
  2. Read ## Development in CHANGES.md. If it is empty, stop: a version with no entries has no release notes. Use the check-changes skill first.
  3. Set the version. It moves the entries under the version, and prints the changed files as JSON.

    uv run scripts/version/version.py bump $version

    Exit 2 means the version is wrong. Exit 1 means that a place states no version or that CHANGES.md breaks a limit, and no file changed. In both cases, report the message and stop.

  4. Check every place against the new version:

    uv run scripts/version/version.py check --tag v$version
  5. Read git diff. Only the version and the new heading may change. If anything else changed, stop and report it.
  6. Commit, if the user asked for a commit: release: $version. Do not tag and do not push. A person cuts the tag on main, after develop merges there, because the tag starts the release workflow and publishes the binaries.

Done when

  • version.py check --tag v$version exits with 0.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.