agentleFS
AI-AnswerAI-Answer/Agent-Club/.claude/skills/bump-version/SKILL.md

bump-version

Skill9 starsChanged 8 months agoApache-2.0View on GitHub

Use when bumping the AionUi version: update package.json, run checks, branch, commit, push, create PR, wait for merge, tag release.

  • Commits and pushes

42 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 38 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    Read package.json → extract version field.

    line 37
  2. Distinctive:

    Use Edit tool to replace:

    line 46
  3. Distinctive:

    Check if remote branch still exists:

    line 102

“Common” is measured: kept by at least 6 in 10 of the 38 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

Automate the AionUi version bump workflow: update version → quality checks → branch → commit → push → PR → tag.

Usage: /bump-version [version]

  • /bump-version 1.8.17 — bump to specified version
  • /bump-version — auto-increment patch (e.g. 1.8.16 → 1.8.17)

Workflow

Step 1: Pre-flight Checks

git branch --show-current
git status --short
  • Not on main → Stop: "Please switch to main before running bump-version."
  • Dirty working tree → Stop: "There are uncommitted changes. Please commit or stash them first."

Step 2: Pull Latest

git pull --rebase origin main

Fails → Stop: "Failed to pull latest code. Please resolve conflicts or network issues first."

Step 3: Determine Target Version

Read package.json → extract version field.

  • Argument provided → use as-is
  • No argument → parse major.minor.patch, increment patch by 1

Display: "Bumping version: {current} → {target}"

Step 4: Update package.json

Use Edit tool to replace:

  • old: "version": "{current}"
  • new: "version": "{target}"

Step 5: Quality Checks

bun run lint
bun run format
bunx tsc --noEmit
  • lint fails → Stop: "Lint errors found. Please fix them before bumping the version."
  • format → Auto-fixes silently.
  • tsc fails → Stop: "TypeScript errors found. Please fix them before bumping the version."

Step 6: Run Tests

bunx vitest run

Fails → Stop: "Tests failed. Please fix failing tests before bumping the version."

Step 7: Branch, Commit, Push

git checkout -b chore/bump-version-{target}
git add -A
git commit -m "chore: bump version to {target}"
git push -u origin chore/bump-version-{target}

Step 8: Create PR

gh pr create --base main \
  --title "chore: bump version to {target}" \
  --body "Bump version to {target}"

Display PR URL. Then pause:

"PR created: {URL}. Please notify a team member to merge it, then confirm to continue."

Wait for user confirmation before proceeding.

Step 9: Cleanup After Merge

git checkout main
git pull --rebase origin main
git branch -d chore/bump-version-{target}

Check if remote branch still exists:

git ls-remote --heads origin chore/bump-version-{target}
  • Has output → delete remote: git push origin --delete chore/bump-version-{target}
  • No output → skip.

Step 10: Create and Push Tag

git tag v{target}
git push origin v{target}

Display: "Tag v{target} created and pushed. Version bump complete!"

Quick Reference

1. Must be on clean main
2. git pull --rebase
3. Determine target version
4. Edit package.json
5. lint + format + tsc
6. vitest run
7. branch chore/bump-version-{target} → commit → push
8. gh pr create → wait for merge
9. checkout main → pull → delete branch
10. git tag v{target} && git push origin v{target}

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.