skills.rest
dhnt
dhntOFFICIAL
Explore all skills by this author →
GitHub

tag-release

Create and push annotated Git tags for version-bump commits.

Updated Dec 21, 2018
Search Tags:#git#changelog#versioning#github actions#release#tagging#ci validation
One-click install
npx skills add https://github.com/dhnt/dhnt --skill tag-release-dhnt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tag-release
Source: https://github.com/dhnt/dhnt/tree/main/catalog/md/release/tag-release
Command: npx skills add https://github.com/dhnt/dhnt --skill tag-release-dhnt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents broken or confusing releases by guiding you through tagging the correct commit, with the right annotation and on the canonical remote.

Core Features & Use Cases

  • Pre-flight validation: Ensures you are on the correct branch, CI is green for the intended commit, the version-bump and changelog updates are present, and the repo state is clean.
  • Deterministic tag creation: Produces an annotated tag (optionally signed) using the project’s established tag format.
  • Reliable remote publishing: Pushes the tag explicitly and verifies it is visible so downstream release automation can run.
  • Use case: You just merged a version bump and changelog update on your release branch, and you need to publish a new GitHub/GitLab release tag that triggers packaging or deployments.

Quick Start

Run the tag and push checklist for your release branch to create an annotated tag for the version-bump commit and push that tag to origin.

Frequently Asked Questions about tag-release

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

FAQPage Schema
How do I create an annotated git tag for a release commit?▼

An annotated git tag for a release commit is created by verifying a clean repo state, generating the tag with release notes, and explicitly pushing it to the canonical remote. This ensures the correct version-bump commit is tagged and visible to downstream automation.

What is the best way to push a release tag to trigger GitHub Actions?▼

The best way to push a release tag to trigger GitHub Actions is to explicitly push the annotated tag to the canonical remote and verify its visibility. This confirms the tag is published and ready for downstream release automation like packaging or deployments.

Do I need CI to be green before cutting a release tag?▼

Yes, CI needs to be green before cutting a release tag. Pre-flight validation ensures CI passes for the intended commit, the version bump is present, changelogs are updated, and the repo state is clean before tagging.

Does this tagging workflow support both GitHub and GitLab repositories?▼

Yes, this tagging workflow supports both GitHub and GitLab repositories. It fits tagging workflows on release branches across GitHub, GitLab, and similar Git hosting platforms when creating annotated, optionally signed release tags.

How do I ensure my changelog and version bump are included before tagging?▼

To ensure your changelog and version bump are included before tagging, perform pre-flight validation on your release branch. This verifies the version-bump and changelog updates are present in the commit before creating the annotated tag.

Related Skills

Explore More Product & Management Skills→
MartinoPoloMartinoPolo
1

mp-release

Bump npm versions, push tags, and verify GitHub Actions runs.

Community
Intermediate
ruifrvazruifrvaz
3

smaqit.release-git-local

Stage release files, commit, create an annotated tag, and push to remote.

Community
Intermediate
PlagueHOPlagueHO
4

release-changelog

Update CHANGELOG.md and create a release tag from commits since the last version tag.

Community
Advanced
coaguscoagus
2

release-engineering

Coordinate end-to-end PHP library releases with semantic versioning and CI verification.

Community
Advanced