Verified:GitHub

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Updated Mar 29, 2026

Search Tags:#changelog #ci-cd #semantic-release #semantic-versioning #conventional-commits #release-please #automated-versioning

Ready to run

npx skills add https://github.com/marquesfelip/agents-and-skills --skill automated-versioning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: automated-versioning
Source: https://github.com/marquesfelip/agents-and-skills/tree/main/skills/automated-versioning
Command: npx skills add https://github.com/marquesfelip/agents-and-skills --skill automated-versioning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual version management and release processes are error-prone and slow; this skill automates semantic version bumps, changelog generation, and release tagging driven by commit messages.

Core Features & Use Cases

Automated version bumps from conventional commits using semantic-release or release-please.
CHANGELOG generation and release note automation across monorepos and multi-package setups.
Flexible tagging for Docker images and release artifacts, with support for pre-releases and major/minor/patch bumps.

Quick Start

Configure your repository to automatically bump versions and generate release notes from commit messages.

Frequently Asked Questions about automated-versioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate semantic versioning in CI/CD from conventional commits?▼

Automated semantic versioning in CI/CD uses conventional commit messages to derive version bumps and manage releases. This approach automatically parses commit history to determine major, minor, or patch increments and generates release notes without manual intervention.

What is the best way to generate changelogs for a monorepo using release-please?▼

Generating changelogs for a monorepo using release-please involves parsing conventional commits to automatically produce release notes and version bumps. This automates multi-package release management by tracking changes across packages and updating their respective changelogs.

Does semantic-release support pre-releases and Docker image tagging?▼

Semantic-release supports pre-releases and flexible tagging for Docker images and release artifacts. It integrates into CI pipelines to automatically apply major, minor, patch, or pre-release version bumps derived from your commit history.

How do I configure release-please to manage multi-package releases in GitHub Actions?▼

Configuring release-please for multi-package releases in GitHub Actions involves setting up your CI workflow to scan conventional commit messages. This automatically triggers version bumps, generates changelogs, and manages release tags across your monorepo packages.

Can I use conventional commits to automate version bumps without writing manual release notes?▼

Conventional commits can fully automate version bumps without manual release notes by driving tools like semantic-release or release-please. These tools parse commit prefixes like feat and fix to automatically determine the bump level and generate changelog entries.

How does automated versioning handle major, minor, and patch bump strategies?▼

Automated versioning handles bump strategies by mapping conventional commit types to semantic version increments. Breaking changes trigger major bumps, new features trigger minor bumps, and fixes trigger patch bumps, with configurable strategies for pre-releases.