agentleFS
roryeckelroryeckel/wyoming_openai/.agents/skills/bump-version/SKILL.md

bump-version

Skill226 starsChanged 29 days agoApache-2.0View on GitHub

Bump the version number of wyoming-openai.

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

7 rules. 0 are common, 2 are distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 5

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Do not edit pyproject.toml/README.md locally, and do not create the tag.

    line 13
  2. Very specific:

    Use the steps below only when working off a non-main branch, when the Action is unavailable, or for estimate mode.

    line 35
  3. Very specific:

    Read current version from pyproject.toml (line containing version = "x.y.z")

    line 38
  4. Distinctive:

    If no argument provided, default to minor bump

    line 39
  5. Very specific:

    If argument is estimate, analyze changes since last tag to determine bump type:

    line 40
  6. Distinctive:

    Use git log and git diff to review recent changes

    line 41
  7. Very specific:

    Commit the edits. Tag vx.y.z only if you are building release artifacts outside the workflow.

    line 55

“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 version $ARGUMENTS.

Releasing off main — dispatch the workflow

A release is prepared by the Bump Version GitHub Action, not by hand. Do not edit pyproject.toml/README.md locally, and do not create the tag.

  1. Dispatch it (or Actions → Bump Version → Run workflow):
    gh workflow run bump-version.yml -f bump_type=<patch|minor|major>
  2. The Action runs the Home Assistant E2E gate, updates pyproject.toml and README.md, and opens a PR from release/v<new> labeled release-bump.
  3. Optionally set the GitHub release title on the PR body's Release title: line (the version is appended automatically; blank defaults to Release <new>), then merge the PR. The Draft Release workflow re-runs the E2E gate against the merge commit and creates the draft release with generated notes.
  4. Publishing that draft release creates the v<new> tag and fires the PyPI and Docker latest workflows.

The Action fails if release/v<new> already exists on origin; delete a stale release branch before re-dispatching. Use gh run watch <run-id> --exit-status to follow it, then check the new PR with gh pr list.

Local fallback

Use the steps below only when working off a non-main branch, when the Action is unavailable, or for estimate mode.

  1. Read current version from pyproject.toml (line containing version = "x.y.z")
  2. If no argument provided, default to minor bump
  3. If argument is estimate, analyze changes since last tag to determine bump type:
    • Use git log and git diff to review recent changes
    • patch: bug fixes, documentation, minor tweaks
    • minor: new features, non-breaking enhancements
    • major: breaking changes, API modifications
    • Present recommendation to user for confirmation before proceeding
  4. Calculate new version:
    • patch: x.y.z → x.y.(z+1)
    • minor: x.y.z → x.(y+1).0
    • major: x.y.z → (x+1).0.0
  5. Update version in:
    • pyproject.toml: Update version = "x.y.z" line
    • README.md: Update both Docker tagging examples (the x.y.z and x.y tags in section "Docker Tags")
  6. Display summary: old version → new version, files updated
  7. Commit the edits. Tag vx.y.z only if you are building release artifacts outside the workflow.

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.