# 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.

- Skill: `ai-driven-dev/aidd-vcs-03-release-tag` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add ai-driven-dev/aidd-vcs-03-release-tag`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ai-driven-dev/aidd-vcs-03-release-tag/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: ai-driven-dev (https://skillmd.com/u/ai-driven-dev)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ai-driven-dev/aidd-vcs-03-release-tag

---


# 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.