Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Semantic Versioning

  • 484 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

semantic-versioning is a release automation skill that manages SemVer bumps, changelogs, and publishes using conventional commits for developers who need automated package and API releases.

About

semantic-versioning is a Release Management skill from aj-geddes/useful-ai-prompts that implements semantic versioning with automated release management through conventional commits, semantic-release, and version bumping strategies. The overview ties version numbers to release significance and automated release notes generation, and the when-to-use list covers package and library releases, API versioning, and version bump automation. A developer reaches for semantic-versioning when configuring commit message conventions, CI release pipelines, changelog generation, and npm or library publish flows. The skill provides quick start, reference guides, and best practices for maintaining consistent SemVer across teams.

  • Implements full Semantic Versioning (SemVer) rules for major, minor, and patch releases
  • Automates version bumping with conventional commits
  • Generates release notes and changelogs automatically
  • Integrates with GitHub, npm, and other publishing platforms
  • Tracks breaking changes and dependency updates

Semantic Versioning by the numbers

  • 484 all-time installs (skills.sh)
  • Ranked #47 of 248 Release Management skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill semantic-versioning

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs484
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you automate SemVer releases with conventional commits?

Automatically manage version numbers, generate changelogs, and publish releases using conventional commits and semantic-release.

Who is it for?

Maintainers of npm packages, libraries, or versioned APIs who want automated bump, changelog, and publish flows from conventional commits.

Skip if: Repositories without conventional commit discipline or teams that only need manual one-off tags should skip semantic-versioning automation.

When should I use this skill?

A user asks to set up semantic-release, conventional commits, automated changelog generation, or SemVer bump strategies for a library or API.

What you get

SemVer version tags, generated CHANGELOG, semantic-release CI config, and published package or API release artifacts.

  • CHANGELOG
  • version tags
  • release CI configuration

Files

SKILL.mdMarkdownGitHub ↗

Semantic Versioning

Table of Contents

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",
    },
}

Reference Guides

Detailed implementations in the references/ directory:

GuideContents
Semantic Versioning ConfigurationSemantic Versioning Configuration
Conventional Commits FormatConventional Commits Format
Semantic Release ConfigurationSemantic Release Configuration
Version Bumping ScriptVersion Bumping Script
Changelog GenerationChangelog Generation

Best Practices

✅ DO

  • Follow strict MAJOR.MINOR.PATCH format
  • Use conventional commits
  • Automate version bumping
  • Generate changelogs automatically
  • Tag releases in git
  • Document breaking changes
  • Use prerelease versions for testing

❌ DON'T

  • Manually bump versions inconsistently
  • Skip breaking change documentation
  • Use arbitrary version numbering
  • Mix features in patch releases

Related skills

FAQ

What tools does semantic-versioning emphasize?

semantic-versioning centers on conventional commits, semantic-release, and version bumping strategies to align version numbers with release significance and automate notes.

When should semantic-versioning be used?

semantic-versioning fits package and library releases, API versioning, and automated version bump workflows when teams adopt conventional commit messages.

What artifacts does semantic versioning automation produce?

semantic-versioning guides generation of consistent version tags, changelogs, and release notes aligned to SemVer rules through automated release management pipelines.

Release Managementdevopsintegrations

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.