git-release-tagging
Git Release Tagging
Overview
Use this skill to cut releases with immutable tags and auditable change boundaries.
Scope Boundaries
- Use this skill when the task matches the trigger condition described in
description. - Do not use this skill when the primary task falls outside this skill's domain.
Shared References
- Versioning and immutability rules:
references/tag-versioning-and-immutability.md
Templates And Assets
- Release tagging runbook:
assets/release-tagging-runbook-template.md
- Release notes template:
assets/release-notes-template.md
Inputs To Gather
- Target release commit SHA and readiness evidence.
- Versioning policy and reserved tag namespace.
- Approval requirements and release communication needs.
- Rollback strategy if release validation fails post-cut.
Deliverables
- Annotated release tag bound to a specific commit.
- Release notes mapped to bounded commit range.
- Verification record for tag integrity and publication status.
- Traceable release artifact metadata for audit.
Workflow
- Validate preconditions using
assets/release-tagging-runbook-template.md. - Confirm naming and immutability constraints from
references/tag-versioning-and-immutability.md. - Create annotated release tag and verify target commit binding.
- Draft and publish release notes with
assets/release-notes-template.md. - Record post-cut verification and handoff artifacts.
Quality Standard
- Tag naming follows one consistent policy.
- Published tag is immutable and never re-pointed.
- Release notes are bounded, accurate, and actionable.
- Release cut can be traced from tag -> commit range -> notes.
Failure Conditions
- Stop when release commit readiness is not proven.
- Stop when tag naming collides with existing published tags.
- Escalate when immutability cannot be guaranteed on current hosting setup.
More from kentoshimizu/sw-agent-skills
graph-algorithms
Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.
14bash-style-guide
Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
11architecture-clean-architecture
Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.
11powershell-style-guide
Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
10github-codeowners-management
Govern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
9security-authentication
Security workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
9