semantic-versioning
This skill equips AI agents to handle version management workflows by applying semantic versioning conventions to your release pipeline. Streamline version bumping, changelog generation, and release tagging—letting your automation handle the repetitive parts of version control so your team focuses on what matters.
semantic-versioning automates version bumping by analyzing your commit history and applying semantic versioning conventions. When you use conventional commits (feat:, fix:, BREAKING CHANGE:), the skill determines whether to increment the major, minor, or patch version number automatically. Tools like semantic-release and standard-version integrate with your CI/CD pipeline to calculate the next version, create git tags, and trigger releases without manual intervention.
AI-generated summary based on this skill's SKILL.md
Decision gist · record as of 2026-05-22
semantic-versioning automates version bumping by analyzing your commit history and applying semantic versioning conventions. When you use conventional commits (feat:, fix:, BREAKING CHANGE:), the skill determines whether to increment the major, minor, or patch version number automatically. Tools like semantic-release and standard-version integrate with your CI/CD pipeline to calculate the next version, create git tags, and trigger releases without manual intervention.
Use it when
- semantic-versioning uses conventional commits to determine version increments by mapping commit types to semver changes.
- Yes, semantic-versioning generates changelogs automatically from your commit history by extracting and organizing conventional commits.
Verify before relying
Read SKILL.md below before installing (1 file). Open directory: indexed for reading, not audited.
Install
BagelHole/DevOps-Security-Agent-Skills/semantic-versioning · repository language: Shell
Open directory. Skills are indexed for reading, not audited. Review a skill's body before installing it.
Frequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does semantic-versioning automate version bumping?
semantic-versioning automates version bumping by analyzing your commit history and applying semantic versioning conventions. When you use conventional commits (feat:, fix:, BREAKING CHANGE:), the skill determines whether to increment the major, minor, or patch version number automatically. Tools like semantic-release and standard-version integrate with your CI/CD pipeline to calculate the next version, create git tags, and trigger releases without manual intervention.
What is the relationship between conventional commits and version increments in semantic-versioning?
semantic-versioning uses conventional commits to determine version increments by mapping commit types to semver changes. A 'fix:' commit triggers a patch bump, a 'feat:' commit triggers a minor bump, and a commit with 'BREAKING CHANGE:' in the footer triggers a major bump. This standardized commit format allows semantic-versioning to parse your git history automatically and calculate the correct version number without ambiguity or manual decision-making.
Can semantic-versioning generate changelogs automatically from commit history?
Yes, semantic-versioning generates changelogs automatically from your commit history by extracting and organizing conventional commits. Tools configured through this skill parse commits since the last release, group them by type (features, fixes, breaking changes), and format them into a readable changelog. This changelog generation happens as part of the automated release process, ensuring your release notes always reflect the actual changes in each version.
How do you set up a CI/CD release pipeline using semantic-versioning?
semantic-versioning enables CI/CD release pipeline setup by configuring tools like semantic-release or standard-version to run on your repository. You define rules for when releases should trigger (typically on commits to your main branch), and the skill handles version calculation, changelog generation, git tagging, and package publishing automatically. The pipeline integrates with your version control system to detect changes and orchestrate the entire release workflow without manual steps.
Does semantic-versioning support managing versions across multiple packages?
semantic-versioning supports multi-package version management through tools like Lerna and Changesets. These tools allow you to manage interdependent packages within a monorepo, coordinating version bumps across packages and tracking which packages changed in each release. This is particularly useful for projects with multiple related packages that need to stay synchronized or have independent versioning strategies.
What are the major, minor, and patch versioning rules in semantic-versioning?
semantic-versioning follows these semver rules: a major version bump (X.0.0) indicates breaking changes, a minor version bump (x.Y.0) indicates new backward-compatible features, and a patch version bump (x.y.Z) indicates backward-compatible bug fixes. The skill applies these rules automatically based on your conventional commits, so 'BREAKING CHANGE:' commits increment major, 'feat:' commits increment minor, and 'fix:' commits increment patch versions.
SKILL.md
Rendered from the published skill. Quoted content, verbatim.
Semantic Versioning
Automate version management and changelog generation following SemVer principles.
When to Use This Skill
Use this skill when: - Implementing version numbering standards - Automating release versioning - Generating changelogs automatically - Setting up release pipelines - Managing package versions
Prerequisites
- Git repository with commit history
- Node.js (for most tools)
- Conventional commits (recommended)
Semantic Versioning Basics
Version Format
MAJOR.MINOR.PATCH[-PRERELEASE][+BUILD]
Examples:
1.0.0
2.1.3
1.0.0-alpha.1
1.0.0-beta.2+build.123
Version Components
| Component | When to Increment |
|---|---|
| MAJOR | Breaking changes (incompatible API changes) |
| MINOR | New features (backward compatible) |
| PATCH | Bug fixes (backward compatible) |
| PRERELEASE |
(truncated - see the full file via the links below)
File tree — 1 file
devops/release/semantic-versioning/SKILL.md
Let your AI agent find skills like this
Example. Real query, live index.
You found this page by searching. An agent finds it by wishing: SkillFed indexes 56,283 agent skills by what they can do, searchable in plain language.
wish › “Automate version bumping and release processes following semantic versioning standards”
Give your agent the search over MCP, or paste the wish link into any chat. No install? Search from any chat →
Related skills
Master Lerna monorepo setup and management with this comprehensive skill. Learn to initialize projects, configure workspaces, and orchestrate builds across multiple packages efficiently. Ideal for teams scaling JavaScript and TypeScript codebases.
changelog-generator analyzes your Git history and produces structured CHANGELOG.md files following Keep a Changelog standards. It parses commits using Conventional Commits conventions, automatically categorizes changes by type, detects breaking changes, and supports semantic version bumping. Use it to initialize configs, generate full histories, incrementally update unreleased sections, or publish new versions—with optional GitHub Actions integration.
AWS S3 equips you with production-grade bucket configuration, from hardening with encryption and public access blocks to enforcing policies and setting up cross-region replication. Handle lifecycle transitions, presigned URLs, and access control in one skill.
This skill analyzes your staged changes and proposes a split into multiple focused commits, each with a semantic message following conventional patterns. It groups related files by feature, change type, or dependency, then walks you through approval and execution—with a dry-run mode to preview splits before committing.
vllm-server guides you through deploying and configuring vLLM—a high-performance open-source LLM serving engine—for production workloads. Set up continuous batching, multi-GPU tensor parallelism, model quantization, and OpenAI-compatible API endpoints to serve models like Llama and Mistral at scale. Includes Docker deployment, performance tuning, monitoring with Prometheus metrics, and troubleshooting for common VRAM and throughput issues.
LLMOps Platform Engineering teaches you to architect internal LLM platforms that balance rapid experimentation with production safety. You'll implement model promotion pipelines with automated quality and safety gates, canary validation, and rollback capabilities, plus set up A/B testing infrastructure and observability across Kubernetes and cloud inference.
More skills model-serving-kubernetes (MIT) · cis-benchmarks (MIT)