agentleFS
Sign inStart free
rust-worksrust-works/omni-dev/.claude/skills/version-bump/SKILL.md

version-bump

Skill2 starsChanged 39 days agoBSD-3-ClauseView on GitHub

Determines appropriate semantic version bumps based on changes. Use when deciding version numbers, evaluating breaking changes, or planning releases. Triggers on terms like "version", "semver", "breaking change", "major/minor/patch".

26 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use security-audit and commit.

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.
  • CloudflareSkill

    security-audit

    Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.

    Also in 3 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 23 edited versions we read keep these.

  • 5

    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. Distinctive:

    Check for breaking changes:

    line 81
  2. Distinctive:

    If breaking changes exist -> MAJOR bump

    line 86
  3. Distinctive:

    If new features exist -> MINOR bump

    line 88
  4. Distinctive:

    If only fixes/refactoring -> PATCH bump

    line 90
  5. Distinctive:

    When bumping version, update:

    line 94
  6. Very specific:

    CHANGELOG.md: - Run python3 scripts/changelog.py collect --component crate --version X.Y.Z, which adds the ## [X.Y.Z] - YYYY-MM-DD section …

    line 97

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

Semantic Versioning Skill

This skill helps determine appropriate version bumps following Semantic Versioning.

Version Format

MAJOR.MINOR.PATCH
  • MAJOR: Breaking changes
  • MINOR: New features, backwards compatible
  • PATCH: Bug fixes, backwards compatible

Version Bump Decision Tree

MAJOR (X.0.0) - Breaking Changes

Bump MAJOR when you make incompatible API changes:

  • Removed public functions, methods, or types
  • Changed function signatures (parameters, return types)
  • Renamed public APIs
  • Changed default behavior that breaks existing usage
  • Removed CLI flags or changed their meaning
  • Changed configuration file format incompatibly

MINOR (0.X.0) - New Features

Bump MINOR when you add functionality in a backwards compatible manner:

  • New commands or subcommands
  • New CLI flags
  • New configuration options
  • New output formats
  • New integrations or providers

PATCH (0.0.X) - Bug Fixes

Bump PATCH when you make backwards compatible bug fixes:

  • Fix incorrect behavior
  • Fix crashes or errors
  • Performance improvements (no API changes)
  • Documentation fixes
  • Internal refactoring (no behavior changes)

Quick Reference

Change TypeVersion Bump
Breaking API changeMAJOR
Removed featureMAJOR
New command/featureMINOR
New CLI flagMINOR
New provider/integrationMINOR
Bug fixPATCH
Performance fixPATCH
Documentation onlyPATCH
Refactoring (no behavior change)PATCH

Pre-1.0 Versioning

For versions < 1.0.0 (like this project):

  • MINOR can include breaking changes
  • PATCH is for bug fixes and small features
  • More flexibility before reaching stability

Instructions

  1. Review all changes since last release:
    git log --oneline $(git describe --tags --abbrev=0)..HEAD
  2. Check for breaking changes:
    • Removed or renamed public APIs?
    • Changed default behaviors?
    • Incompatible configuration changes?
  3. If breaking changes exist -> MAJOR bump
  4. If new features exist -> MINOR bump
  5. If only fixes/refactoring -> PATCH bump

Version Update Locations

When bumping version, update:

  1. Cargo.toml - version = "X.Y.Z"
  2. CHANGELOG.md - Run python3 scripts/changelog.py collect --component crate --version X.Y.Z, which adds the ## [X.Y.Z] - YYYY-MM-DD section from the changelog.d/ fragments
  3. Version links - collect updates the comparison URLs at the bottom of CHANGELOG.md; check them

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.

Check your setup, free