How do I install the Create Release Tags skill?

Run npx skillmds@latest add kubernetes-sigs/create-release-tags 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 Create Release Tags 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 Create Release Tags?

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 Create Release Tags free to use?

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

Who published Create Release Tags?

kubernetes-sigs (@kubernetes-sigs) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create Release Tags by kubernetes-sigs

Name: Create Release Tags
Author: kubernetes-sigs

Create Release Tags

Create and optionally push the next Kubernetes-style release tag (vX.Y.Z) from a release-X.Y branch by resolving the remote branch tip, computing the next patch tag, and tagging the commit directly without checking out the branch. Use when the user wants to tag a release, create a version tag, or mentions release tagging, cutting a release, or bumping a patch version.

File contents

Push Release Tag

Goal

Cut a new stable release tag for a Kubernetes-style release branch:

Branch: release-X.Y
Tag: vX.Y.Z (patch bump)

Recommended Workflow

Use scripts/create_release_tags.py to:

Fetch the chosen remote and tags
Resolve the commit at the tip of <remote>/release-X.Y
Compute the next stable tag if one is not given explicitly
Create the tag pointing at that commit (no branch checkout required)
Optionally push the tag to the remote

Multiple branches can be tagged in parallel since the script never checks out or modifies the local working tree.

Commands

Replace <SKILL_DIR> with the path of this skill directory.

Plan only:

python3 <SKILL_DIR>/scripts/create_release_tags.py --repo . --branch release-1.34

Create the tag locally:

python3 <SKILL_DIR>/scripts/create_release_tags.py --repo . --branch release-1.34 --create

Create and push the tag:

python3 <SKILL_DIR>/scripts/create_release_tags.py --repo . --branch release-1.34 --push

Notes

Default remote is upstream. Override with --remote <name>.
If the branch name does not match release-X.Y, pass --series X.Y.
Tags are annotated by default. Use --sign for signed tags.
--force-branch is a no-op kept for backward compatibility.

Manual Fallback

Fetch the remote branch and tags:

git fetch upstream --prune --tags

Find the latest stable tag merged into the branch:

git tag --merged upstream/release-1.34 --list 'v1.34.*' --sort=version:refname | grep -E '^v1\.34\.[0-9]+$' | tail -n1

Create and push an annotated tag at the remote branch tip:

git tag -a -m "v1.34.7" v1.34.7 upstream/release-1.34
git push upstream v1.34.7

Safety Checks

Ensure the computed tag does not already exist.
Push only the intended tag, not every local tag.

---name: create-release-tagsdescription: Create and optionally push the next Kubernetes-style release tag (vX.Y.Z) from a release-X.Y branch by resolving the remote branch tip, computing the next patch tag, and tagging the commit directly without checking out the branch. Use when the user wants to tag a release, create a version tag, or mentions release tagging, cutting a release, or bumping a patch version.---# Push Release Tag## GoalCut a new stable release tag for a Kubernetes-style release branch:- Branch: `release-X.Y`- Tag: `vX.Y.Z` (patch bump)## Recommended WorkflowUse `scripts/create_release_tags.py` to:1. Fetch the chosen remote and tags2. Resolve the commit at the tip of `<remote>/release-X.Y`3. Compute the next stable tag if one is not given explicitly4. Create the tag pointing at that commit (no branch checkout required)5. Optionally push the tag to the remoteMultiple branches can be tagged in parallel since the script never checks outor modifies the local working tree.## CommandsReplace `<SKILL_DIR>` with the path of this skill directory.Plan only:```bashpython3 <SKILL_DIR>/scripts/create_release_tags.py --repo . --branch release-1.34```Create the tag locally:```bashpython3 <SKILL_DIR>/scripts/create_release_tags.py --repo . --branch release-1.34 --create```Create and push the tag:```bashpython3 <SKILL_DIR>/scripts/create_release_tags.py --repo . --branch release-1.34 --push```## Notes- Default remote is `upstream`. Override with `--remote <name>`.- If the branch name does not match `release-X.Y`, pass `--series X.Y`.- Tags are annotated by default. Use `--sign` for signed tags.- `--force-branch` is a no-op kept for backward compatibility.## Manual FallbackFetch the remote branch and tags:```bashgit fetch upstream --prune --tags```Find the latest stable tag merged into the branch:```bashgit tag --merged upstream/release-1.34 --list 'v1.34.*' --sort=version:refname | grep -E '^v1\.34\.[0-9]+$' | tail -n1```Create and push an annotated tag at the remote branch tip:```bashgit tag -a -m "v1.34.7" v1.34.7 upstream/release-1.34git push upstream v1.34.7```## Safety Checks- Ensure the computed tag does not already exist.- Push only the intended tag, not every local tag.

Frequently asked questions