agentleFS
GavinGreenwoodGavinGreenwood/agentic-workflow-template/.agents/skills/bump-version/SKILL.md

bump-version

Skill5 starsChanged 44 days agoMITView on GitHub

User-invoked only. Bump main's semver tag by one minor version and push the new tag.

  • Commits and pushes

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

3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run this before anything else, and do not act on any later step until you have its output.

    line 10
  2. Distinctive:

    If git status --porcelain shows any uncommitted changes, stop and tell the user to commit or stash first.

    line 24
  3. Distinctive:

    If nothing matches, stop and ask the user what the starting version should be.

    line 33

“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

Step 0 — Context (required first)

Run this before anything else, and do not act on any later step until you have its output. If a probe fails, stop and tell the user. Never assume these values.

echo "Current branch: $(git branch --show-current)"
echo "Uncommitted changes:"; git status --porcelain
echo "Latest semver tags reachable from main:"; git tag --list --merged main | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$' | sort -V | tail -5

Your Task

This command always bumps the minor (middle) number and resets the patch to 0 — e.g. 0.7.0 → 0.8.0. This is a deliberate hardcoded simplification for now; it does not inspect commit history to decide whether a major or patch bump would be more correct. There is no code change and nothing to commit — this is a tag-only operation.

Step 1 — Get on latest main

  • If git status --porcelain shows any uncommitted changes, stop and tell the user to commit or stash first. Do not tag over a dirty working tree.
  • git checkout main
  • git pull
  • git fetch --tags --prune-tags — make sure local tags match origin, in case someone else already bumped since you last fetched.

Step 2 — Find the current version

  • git tag --list --merged main | grep -E '^[0-9]+\.[0-9]+\.[0-9]+$' | sort -V | tail -1
  • This strict X.Y.Z filter is intentional — a repo's tag history can accumulate malformed/noise tags (e.g. a v-prefixed duplicate, a typo'd tag). Ignore anything that doesn't match exactly.
  • If nothing matches, stop and ask the user what the starting version should be. Do not guess a starting point.

Step 3 — Compute the new version

  • Parse X.Y.Z from the tag found in Step 2.
  • New version is X.(Y+1).0.
  • Example: 0.7.0 → 0.8.0.

Step 4 — Tag and push

  • git tag <new-version> on the current main HEAD.
  • git push origin <new-version>.
  • If the push is rejected by the local pre-push hook, stop and ask the user to confirm before retrying with git push origin <new-version> --no-verify. The hook runs the full lint/typecheck/test pipeline, which doesn't apply to a tag-only push with no file changes, but per AGENTS.md rule 6 --no-verify still requires explicit approval each time. Do not use --no-verify for anything else this command doesn't explicitly cover.

Step 5 — Report

Tell the user the old version, the new version, and confirm the tag was pushed to origin.

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.