kata-tag

What problem does it solve?

This Skill removes the risk of releasing with malformed version identifiers or unsigned/lightweight tags by guiding you through producing a SemVer-compliant, annotated, GPG-signed Git tag that matches the repository’s lex rules.

Core Features & Use Cases

• Checks repository state: verifies a clean working tree and resolves the correct target commit (HEAD by default or a user-specified commit/message).
• Determines the next version: suggests or uses a specific MAJOR.MINOR.PATCH identifier by analyzing changes since the latest SemVer tag and applying lex-semantic-version rules.
• Validates before tagging: confirms the version format and ensures the tag does not already exist.
• Creates the correct tag type: creates an annotated and signed tag using git tag -s with a release message tied to the resolved commit.
• Performs final verification: confirms existence and GPG signature validity, then instructs how to publish the tag to the remote.

Use case example: You need to cut a new release after merging multiple changes, and you want the tag to be automatically derived from commit types while guaranteeing that it is signed and pushable without violating lex-annotated-tags.

Quick Start

Tell the AI: “Create an annotated and GPG-signed release tag for the next Semantic Version at HEAD using lex-semantic-version rules, and verify that the tag is signed before telling me what to push.”