03-release-tag — Claude Code skill for SemVer releases
03-release-tag is a Claude Code skill that prepares SemVer releases from recent commits, updates version files, and creates annotated tags after you review the release details.
MIT ★ 571 updated 2026-10-29
/plugin marketplace add ai-driven-dev/framework
/plugin install aidd-vcs@aidd-frameworkWhat 03-release-tag does
The skill takes a release from version selection through tag creation. It drafts release notes from recent commits, validates them, updates version-manager files, then creates and pushes an annotated Git tag. Notes are required and use assets/release-template.md.
Before tagging, the agent asks you to review the version, notes, and affected files. Versions must use the major.minor.patch SemVer format; suffixes are allowed only when explicitly requested. The version bump commit contains only version-manager files, and tags must not be pushed with --force. This workflow is for cutting a release, not for a plain commit or pull request.
What it helps with
- draft release notes from recent commits
- check a version before creating its tag
- update version-manager files for a release
- create and push an annotated Git tag
Example prompts for the agent
- Prepare a release for version
1.2.3, draft the notes, and show me which files will change. - Cut a release based on recent commits and ask for my approval before tagging.
How to install 03-release-tag
1Plugin marketplace
/plugin marketplace add ai-driven-dev/framework/plugin install aidd-vcs@aidd-frameworkThis installs the whole aidd-vcs plugin with all its skills
2Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 03-release-tag -a claude-code3Manually: put the files in place
~/.claude/skills/03-release-tag/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/03-release-tag/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 03-release-tag -a codex2Manually: put the files in place
.agents/skills/03-release-tag/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 03-release-tag -a cursor2Manually: put the files in place
.cursor/skills/03-release-tag/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ai-driven-dev/framework plugins/aidd-vcs/skills/03-release-tag2Manually: put the files in place
.github/skills/03-release-tag/SKILL.md1Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 03-release-tag -a gemini-cli2Platform CLI
gemini skills install https://github.com/ai-driven-dev/framework --path plugins/aidd-vcs/skills/03-release-tagManually: put the files in place
.devin/skills/03-release-tag/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ai-driven-dev/framework --skill 03-release-tag -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about 03-release-tag
How do I install 03-release-tag in Claude Code?
Add the marketplace with /plugin marketplace add ai-driven-dev/framework, then install the plugin with /plugin install aidd-vcs@aidd-framework.
What does 03-release-tag do?
It drafts notes from recent commits, updates version-manager files, and creates an annotated SemVer tag. Before tagging, it asks you to review the version, notes, and affected files.
What version format does 03-release-tag use?
Versions use the major.minor.patch format. A suffix is permitted only when explicitly requested.
Source text
SKILL.md · MIT
--- name: 03-release-tag description: Cut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag. argument-hint: version --- # Release Tag Cuts annotated semver releases with notes derived from recent commits. ## Actions | # | Action | Role | Input | | --- | -------------- | -------------------------------------------------------------------------- | ---------------------------------- | | 01 | `release-tag` | Compute version, draft notes, validate, bump, tag, push | version (optional), notes_overrides| Before running an action, read its file in `actions/`, not only the table or assets. ## 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`). ## Assets - `assets/release-template.md`: Release notes template.
© AI-Driven Dev · MIT · ai-driven-dev/framework