git-tag

Name: git-tag
Availability: InStock
Author: MakerLabs

Create and push date-based Git release tags with incremental daily suffixes.

Updated Apr 22, 2026

Search Tags:#automation #git #workflow #versioning #release #ci-cd #tagging

Ready to run

npx skills add https://github.com/mkrlabs/specflow --skill git-tag

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-tag
Source: https://github.com/mkrlabs/specflow/tree/main/examples/.claude/skills/git-tag
Command: npx skills add https://github.com/mkrlabs/specflow --skill git-tag

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automatically create and push a date-based release tag to Git, removing manual guesswork and reducing the risk of tagging mistakes.

Core Features & Use Cases

Date-based tag generation in the format vYY.M.D[a-z]
Incremental daily suffix letter to a, b, c within a day
Annotated tag creation and push to origin
Optional commit specification (HEAD or SHA) and summary output
Validation against the required regex before push

Quick Start

Tag the current HEAD or a specified commit with the next date-based release tag and push it to the remote.

Frequently Asked Questions about git-tag

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

FAQPage Schema

How do I automatically generate date-based Git tags for my release workflow?▼

You can automatically generate date-based Git tags by creating annotated tags in the vYY.M.D[a-z] format and pushing them to your remote repository. This removes manual guesswork and ensures strict regex validation before pushing.

What is the vYY.M.D[a-z] format for Git release tagging?▼

The vYY.M.D[a-z] format is a date-based versioning scheme where the tag reflects the year, month, and day, appending an incremental letter like a, b, or c for multiple releases on the same day to maintain chronological order.

Can I tag a specific commit SHA instead of HEAD in my CI/CD pipeline?▼

Yes, you can specify an optional commit SHA to tag instead of HEAD. This allows you to target specific commits across multiple repositories within your CI/CD pipeline while ensuring the tag format remains valid.

How do I increment daily Git tags for multiple releases on the same day?▼

To increment daily Git tags for multiple releases, the system fetches existing tags and computes the daily suffix increment. It automatically applies the next sequential letter from a, b, c to the date-based tag for that specific day.

Does this date-based tagging approach work across multiple Git repositories?▼

Yes, this date-based tagging approach handles release tagging workflows across multiple repositories. It fetches existing tags from the remote, applies the validated format, and pushes the annotated tag to the origin repository.

What happens if a manually created Git tag does not match the required format?▼

If a Git tag does not match the required format, the validation step against the strict regex will fail before the push. This prevents invalid tags from being pushed to the origin remote and breaking the release workflow.