Skip to content
TrustedSkillsbeta
Back to all skills

Semver Release

Checked
vamdawn·vlatest·backend·MIT

Automates semantic versioning (SemVer) of releases, ensuring consistent and predictable software updates for improved stability and tracking.

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 vamdawn/ai-forge --skill semver-release -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

vamdawn

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 vamdawn/ai-forge at 26749c5bb6.

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

Commit
26749c5bb6
Manifest
skills/semver-release/SKILL.md
Scanned
4 files, 607 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 automates semantic version release processes. It handles incrementing versions, generating changelogs, and tagging releases in Git repositories based on provided commit messages or other criteria. This streamlines the software delivery pipeline by reducing manual effort and ensuring consistent versioning practices.

When to use it

  • Automating minor/patch/major version bumps after merging feature branches.
  • Generating release notes from structured commit messages (e.g., using conventional commits).
  • Tagging Git repositories with semantic versions upon successful builds or deployments.
  • Creating pre-release versions for testing and feedback.

Key capabilities

  • Semantic Version Incrementing (major, minor, patch)
  • Git Tag Creation
  • Changelog Generation
  • Conventional Commit Support

Example prompts

  • "Release version 1.2.3 with changelog from commit messages."
  • "Bump the patch version and create a Git tag."
  • "Generate a pre-release candidate tagged as '1.0.0-rc.1'."

Tips & gotchas

The skill requires access to a Git repository and may need configuration to understand your project's commit message conventions for accurate changelog generation. Ensure the AI agent has appropriate permissions to modify the repository.