Skip to content
TrustedSkillsbeta
Back to all skills

Semantic Versioning

Checked
bagelhole·vlatest·backend·MIT

This skill automatically generates semantic version numbers for your projects, ensuring consistent and organized releases for better tracking & collaboration.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add bagelhole/devops-security-agent-skills --skill semantic-versioning -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

bagelhole

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned bagelhole/devops-security-agent-skills at 0365f57a07.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
0365f57a07
Manifest
devops/release/semantic-versioning/SKILL.md
Scanned
1 file, 440 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps AI agents understand and apply semantic versioning (SemVer). It can parse version strings, determine the next appropriate version number based on increment type (major, minor, or patch), and explain the meaning of different SemVer versions. The skill enables accurate tracking and communication of software changes.

When to use it

  • Automating Release Processes: Increment a version number automatically after merging code into a release branch.
  • Dependency Management: Determine compatible dependency versions based on declared ranges in package manifests (e.g., package.json).
  • Explaining Version Changes: Generate clear explanations of why a specific version bump was necessary for a project.
  • Validating Version Strings: Confirm if a given string adheres to the SemVer specification.

Key capabilities

  • Parses semantic version strings (e.g., 1.2.3).
  • Determines next version based on increment type (major, minor, patch).
  • Explains the meaning of different SemVer versions.
  • Validates if a string is a valid semantic version.

Example prompts

  • "What's the next version after 2.1.4 with a minor bump?"
  • "Is 'v5.0.0-beta.1+build.123' a valid semantic version?"
  • "Explain what a major version change signifies in SemVer."

Tips & gotchas

The skill assumes familiarity with the basic principles of semantic versioning. While it can validate, it doesn’t provide guidance on when to use each increment type (major, minor, patch).