tag-manager

Create and push semantic version tags with GPG signing support.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/fractary/claude-plugins --skill tag-manager
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tag-manager
Source: https://github.com/fractary/claude-plugins/tree/main/plugins/repo/skills/tag-manager
Command: npx skills add https://github.com/fractary/claude-plugins --skill tag-manager

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, jq, and includes scripts (resource) components.

What problem does it solve?

Creates and pushes semantic version tags with optional signing and safe push flows.

Core Features & Use Cases

  • Validate semantic tag format
  • Annotated tags and optional GPG signing
  • Push tags to remote with safety checks

Quick Start

Tag a new release version and push to origin with an annotated message.

Frequently Asked Questions about tag-manager

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create and push semantic version tags with Git?

Semantic version tags are standardized release markers (e.g., v1.2.3) that follow a major.minor.patch format. This Skill creates annotated tags, optionally signs them with GPG, validates the format, checks for duplicates, and safely pushes them to your remote repository while enforcing semantic versioning rules.

Can I sign Git tags with GPG when creating releases?

Yes. This Skill supports optional GPG signing for annotated tags, verifying your GPG configuration before signing and producing signed, cryptographically verified release markers that prove authorship and integrity.

What safety checks does semantic version tagging include?

The Skill validates semantic version format, checks whether tags already exist, verifies commit validity, confirms message structure, and performs safe push flows to prevent accidental overwrites or conflicts with existing releases.

How do I automate release tagging across different Git platforms?

This Skill delegates platform-specific Git operations to active handlers, enabling consistent semantic version tagging and pushing workflows across GitHub, GitLab, and other repository platforms with unified validation and signing.

What Git and command-line tools do I need to use semantic version tagging?

You need bash for script execution and jq for structured JSON processing. These handle tag creation, annotation, GPG signing verification, and result formatting across your release workflow.

When should I use annotated tags instead of lightweight tags for releases?

Annotated tags store metadata like tagger name, date, and optional GPG signatures, making them ideal for semantic version releases where you need provenance, signing, and structured release information embedded in the tag itself.