semantic-release-tagger

Semantic versioning automation analyzes conventional commits (feat, fix, BREAKING) to compute version bumps, then creates annotated tags following npm-style @, slash-based, or flat v conventions. This Skill detects your repository structure, calculates MAJOR.MINOR.PATCH increments, and generates tags with optional GitHub releases—eliminating manual tagging errors across multi-component projects.

Yes. This Skill supports multiple tag conventions—npm-style namespacing (@org/package), slash-based paths, and flat v-prefixed tags—allowing you to apply consistent SemVer rules across components regardless of their naming scheme. It auto-detects which convention your repository uses.

Conventional commit parsing scans commit messages for feat, fix, and BREAKING keywords to determine version increments. Feat commits trigger MINOR bumps, fix commits trigger PATCH bumps, and BREAKING changes trigger MAJOR bumps. This follows SemVer rules to automatically compute the next version number.

GitHub release generation is optional and requires your confirmation. After version calculation and tag creation, you can choose to generate a changelog-driven release on GitHub. The Skill creates annotated tags regardless; releases are an additional step you opt into.

Yes. This Skill integrates with CI/CD by automating tag creation, enforcing annotated tags, and pushing to remote—all steps that fit into workflow automation. You configure it to run in your pipeline after commit analysis, eliminating manual intervention in release tagging.

Manual tagging is error-prone and inconsistent across team members. Automated semantic versioning applies consistent SemVer rules, detects version bumps from commit history, and creates tags deterministically. This eliminates human error and ensures every release follows the same versioning logic.