Create annotated GPG-signed Git release tags with SemVer 2.0 rules.
npx skills add https://github.com/guardiatechnology/design-system --skill kata-tag
Please help me install this Agent Skill. Skill: kata-tag Source: https://github.com/guardiatechnology/design-system/tree/main/.claude/skills/kata-tag Command: npx skills add https://github.com/guardiatechnology/design-system --skill kata-tag
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.
git tag -s with a release message tied to the resolved commit.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.
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.”
High-intent search queries and answers about installing and using this skill.
To create a GPG-signed Git tag, resolve a target commit, compute the next SemVer 2.0 version from history, verify a clean repository state, and execute `git tag -s <version> <target> -m "<message>"` followed by signature validation.
Annotated Git tags store metadata like the tagger's name, date, and a release message, and can be GPG-signed using `git tag -s`. Lightweight tags are simple pointers without metadata or cryptographic signatures, making annotated tags necessary for compliant release workflows.
You can determine the next SemVer version by analyzing commit changes since the latest SemVer tag and applying lex-semantic-version rules to calculate the correct MAJOR.MINOR.PATCH increment before creating the annotated Git tag.
Yes, you need a clean working tree to create a signed release tag. The process requires clean repository state validation to ensure the target commit is stable before executing `git tag -s` and verifying the GPG signature.
Yes, you can validate a GPG-signed Git tag by performing post-creation verification via tag listing and signature validation commands to confirm both the tag's existence and the cryptographic signature's integrity before pushing to the remote.
Creating a Git tag that already exists will fail. The tagging process validates before execution by confirming the version format and checking existing tags to avoid duplicates, ensuring your release workflow does not overwrite previous Semantic Versioning releases.
whatwedoGenerates a synchronized CHANGELOG entry and GPG-signed tag for dde releases.
Conceptual-MachinesCreate and push a v-prefixed git tag on the main branch.
sgcarstrendsGenerate CHANGELOG.md from conventional commits using semantic-release.
vincent-kkAnalyze Git tags in a monorepo to locate release-worthy tags and prepare release notes.