Semantic Versioning

This gets you set up with proper semantic versioning and automated release management using semantic-release and conventional commits. You'll use it when you're shipping packages, managing API versions, or just tired of manually bumping version numbers and writing changelogs. The skill includes configs for semantic-release with changelog and git plugins, plus examples of conventional commit formats that trigger the right version bumps (feat for minor, fix for patch, breaking changes for major). The quick start shows a minimal package.json setup, and there are separate guides for each piece of the toolchain. Honestly, once you commit to the conventional commit format, the automation mostly just works and saves you from versioning mistakes.

skills.sh installs: 552
GitHub stars: 379
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add aj-geddes/useful-ai-prompts --skill semantic-versioning --agent claude-code

Installs into .claude/skills of the current project.

Files

Overview

Establish semantic versioning practices to maintain consistent version numbering aligned with release significance, enabling automated version management and release notes generation.

When to Use

Package and library releases
API versioning
Version bumping automation
Release note generation
Breaking change tracking
Dependency management
Changelog management

Quick Start

Minimal working example:

# package.json
{
  "name": "my-awesome-package",
  "version": "1.2.3",
  "description": "An awesome package",
  "main": "dist/index.js",
  "repository": { "type": "git", "url": "https://github.com/org/repo.git" },
  "scripts": { "release": "semantic-release" },
  "devDependencies":
    {
      "semantic-release": "^21.0.0",
      "@semantic-release/changelog": "^6.0.0",
      "@semantic-release/git": "^10.0.0",
      "@semantic-release/github": "^9.0.0",
      "conventional-changelog-cli": "^3.0.0",
    },
}