How do I install the Aidd Vcs:03:release Tag skill?

Run npx skillmds@latest add ai-driven-dev/aidd-vcs-03-release-tag in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Aidd Vcs:03:release Tag safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Aidd Vcs:03:release Tag?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Aidd Vcs:03:release Tag free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Aidd Vcs:03:release Tag?

ai-driven-dev (@ai-driven-dev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Aidd Vcs:03:release Tag by ai-driven-dev

Name: Aidd Vcs:03:release Tag
Author: ai-driven-dev

Aidd Vcs:03:release Tag

Cut a semver release by computing the next version from recent commits, generating annotated release notes from the template, validating with the user, then creating and pushing the git tag along with a bump commit. Use when the user says "release", "tag", "tag this release", "bump version", "release v1.2.0", "cut a release", or invokes `/release-tag`. Do NOT use for plain commits without a tag, opening pull requests, pushing a branch only, or amending existing tags.

ai-driven-dev c133ace 4 files · 4.9 KB Updated Sep 17, 2026

File contents

Release Tag

Generates and pushes annotated semver tags with release notes. Computes the next version from conventional commits since the previous tag, fills the release notes template, captures user approval, creates a chore: bump version commit, then tags and pushes.

Available actions

#	Action	Role	Input
01	`release-tag`	Compute version, draft notes, validate, bump, tag, push	version (optional), notes_overrides

Default flow

Single action skill. The router dispatches to release-tag whenever a release or tag phrase appears.

Transversal rules

Versions follow semver major.minor.patch strictly. No suffixes unless explicitly requested.
Tags are annotated (git tag -a), never lightweight.
Release notes are mandatory and follow assets/release-template.md.
Always ask the user to validate the version, notes, and impacted files before tagging.
Never --force push tags. Use --force-with-lease only when explicitly required.
The bump commit only includes version-manager files (e.g. package.json, pyproject.toml).

References

None.

Assets

assets/release-template.md: Release notes template.

External data

None.

---name: aidd-vcs-03-release-tagdescription: Cut a semver release by computing the next version from recent commits, generating annotated release notes from the template, validating with the user, then creating and pushing the git tag along with a bump commit. Use when the user says "release", "tag", "tag this release", "bump version", "release v1.2.0", "cut a release", or invokes `/release-tag`. Do NOT use for plain commits without a tag, opening pull requests, pushing a branch only, or amending existing tags.---# Release TagGenerates and pushes annotated semver tags with release notes. Computes the next version from conventional commits since the previous tag, fills the release notes template, captures user approval, creates a `chore: bump version` commit, then tags and pushes.## Available actions| # | Action | Role | Input || --- | -------------- | -------------------------------------------------------------------------- | ---------------------------------- || 01 | `release-tag` | Compute version, draft notes, validate, bump, tag, push | version (optional), notes_overrides|## Default flowSingle action skill. The router dispatches to `release-tag` whenever a release or tag phrase appears.## Transversal rules- Versions follow semver `major.minor.patch` strictly. No suffixes unless explicitly requested.- Tags are annotated (`git tag -a`), never lightweight.- Release notes are mandatory and follow `assets/release-template.md`.- Always ask the user to validate the version, notes, and impacted files before tagging.- Never `--force` push tags. Use `--force-with-lease` only when explicitly required.- The bump commit only includes version-manager files (e.g. `package.json`, `pyproject.toml`).## References- None.## Assets- `assets/release-template.md`: Release notes template.## External data- None.

Frequently asked questions