git-release-tagging

Create immutable annotated release tags bound to specific commits.

7|Updated Feb 14, 2026

Search Tags:#automation #git #changelog #verification #audit #immutability #release-tagging

Ready to run

npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill git-release-tagging

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-release-tagging
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/git-release-tagging
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill git-release-tagging

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This skill enables teams to cut releases with immutable tags and bounded changelog traceability, ensuring auditability and preventing retroactive tag changes.

Core Features & Use Cases

Immutable tagging: creates annotated tags bound to a specific commit with verifiable message and publication record.
Release notes mapping: generates and attaches release notes bounded to the commit range for audit and compliance.
Governance and rollback: enforces naming policies and provides a rollback plan when release validation fails.

Quick Start

Create an annotated release tag for a specific commit and generate auditable release notes and verification artifacts.

Frequently Asked Questions about git-release-tagging

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

FAQPage Schema

How do I create immutable git release tags with auditable traceability?▼

You create immutable git release tags by applying annotated tags bound to a specific commit, capturing release metadata for audit, rollback, and compliance to prevent retroactive changes.

What is the best way to generate release notes bounded to a git commit range?▼

The best way to generate release notes bounded to a commit range is to map the changelog to the specific commit range and attach the traceable notes to the immutable tag for audit and compliance.

Can I enforce git tag naming policies for release management?▼

Yes, you can enforce git tag naming policies during the release tagging process to ensure governance, applying consistent naming conventions across immutable tags before capturing release metadata.

How do I rollback a release when validation fails using git tags?▼

To rollback a release when validation fails, utilize the captured release metadata and immutable tags to execute a governed rollback plan, ensuring the system reverts to the correct previous commit state.

Do I need annotated tags for git release audit and compliance?▼

Annotated tags are required for git release audit and compliance because they bind verifiable messages and publication records to a specific commit, creating the immutable archive needed for traceability.