dot-ai-tag-release

Create semantic version release tags from changelog.d fragments.

2|Updated Dec 8, 2025
One-click install
npx skills add https://github.com/vfarcic/dot-ai-website --skill dot-ai-tag-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dot-ai-tag-release
Source: https://github.com/vfarcic/dot-ai-website/tree/main/.claude/skills/dot-ai-tag-release
Command: npx skills add https://github.com/vfarcic/dot-ai-website --skill dot-ai-tag-release

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of creating version tags for releases, ensuring semantic versioning compliance and streamlining the release workflow.

Core Features & Use Cases

  • Changelog Analysis: Aggregates changelog fragments to determine the correct version bump (major, minor, patch).
  • Semantic Versioning: Enforces semantic versioning based on the type of changes (breaking, feature, bugfix).
  • Release Preparation: Handles commits with [skip ci] to ensure release workflows are triggered.
  • Use Case: After merging several pull requests with changelog entries, run this skill to automatically determine the next version number, create an annotated tag, and push it to the repository.

Quick Start

Run the dot-ai-tag-release skill when you are ready to cut a new release.

Frequently Asked Questions about dot-ai-tag-release

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

FAQPage Schema
How do I automate semantic versioning and release tagging from changelog fragments?

Automate semantic versioning by analyzing changelog fragments in the `changelog.d/` directory to determine the correct version bump (major, minor, or patch), then automatically create and push an annotated release tag to your repository.

How does semantic version bumping work with changelog fragments?

Semantic version bumping works by aggregating changelog fragments to evaluate the type of changes, automatically enforcing a major, minor, or patch version increment based on whether the updates are breaking changes, new features, or bugfixes.

How do I trigger a release workflow when my last commit contains skip ci?

To trigger a release workflow with a skip ci commit, the skill handles the commit by creating a separate preparation commit before tagging, ensuring your CI release pipelines are still executed properly after the tag is pushed.

Can I use this skill to cut a new release after merging multiple pull requests?

Yes, you can use this skill to cut a new release after merging pull requests, as it aggregates the accumulated changelog entries to determine the appropriate next version number, create the tag, and push it to the repository.

Do I need to manually specify the version number when creating a release tag?

No, you do not need to manually specify the version number, because the skill automatically determines the appropriate semantic version bump by analyzing the contents of your accumulated changelog fragments.