git-release-tag-deploy

Creates git branches and pushes semantic version release tags to origin.

Updated Jul 13, 2026

Search Tags:#git #versioning #release #semantic versioning #branch #deploy #tag

Ready to run

npx skills add https://github.com/Ohmnia/site-build --skill git-release-tag-deploy-ohmnia

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: git-release-tag-deploy
Source: https://github.com/Ohmnia/site-build/tree/main/.opencode/skills/git-release-tag-deploy
Command: npx skills add https://github.com/Ohmnia/site-build --skill git-release-tag-deploy-ohmnia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing git branches and release versioning manually is error-prone, especially when calculating the next semantic version and keeping tags in sync with the remote repository. This Skill automates branch creation and SemVer-based release tagging so releases stay consistent. ## Core Features & Use Cases - Branch Creation: Creates a new branch from an up-to-date main and pushes it to origin with upstream tracking. - Semantic Version Tagging: Fetches existing tags, computes the next major, minor, or patch version, and creates an annotated tag with release notes. - Use Case: After merging a feature, ask for a minor release; the Skill detects the latest tag (e.g., v1.2.3), bumps it to v1.3.0, tags it with your release notes, and pushes it to origin. ## Quick Start Create a patch release tag with the note "fix login redirect bug" and push it to origin.

Frequently Asked Questions about git-release-tag-deploy

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

FAQPage Schema

How do I create a semantic version release tag in git?▼

Fetch existing tags with git fetch --tags, find the latest tag using git describe, increment the major, minor, or patch component, then create an annotated tag with git tag -a and push it to origin.

How do I create and push a new git branch from main?▼

Checkout main, pull the latest changes from origin, then run git checkout -b with your branch name and push it using git push -u origin to set up upstream tracking.

What happens if no git tags exist yet when releasing?▼

The versioning logic defaults to v0.0.0 when no tags are found, so the first patch release becomes v0.0.1, the first minor becomes v0.1.0, and the first major becomes v1.0.0.

Can I add release notes to a git tag?▼

Yes, annotated tags created with git tag -a accept a message via the -m flag. If no release notes are provided, the message defaults to the new tag name itself.

Why does git tag versioning fail with an invalid increment type?▼

The increment type must be exactly major, minor, or patch. Any other value triggers an error and exits without creating a tag, preventing accidental or malformed version bumps.