skills.rest
Ohmnia
OhmniaCOMMUNITY
Explore all skills by this author →
GitHub

git-release-management

Automates git branch creation, semantic version tagging, and release checklist validation.

Updated Jul 13, 2026
Search Tags:#git#release management#version control#deployment#branching#semantic versioning#git tag
One-click install
npx skills add https://github.com/Ohmnia/site-build --skill git-release-management-ohmnia
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-release-management
Source: https://github.com/Ohmnia/site-build/tree/main/.opencode/skills/git-release-management
Command: npx skills add https://github.com/Ohmnia/site-build --skill git-release-management-ohmnia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Managing releases manually leads to inconsistent version numbers, mismatched version strings across project files, and accidental commits to protected branches. This Skill enforces a disciplined git workflow with semantic versioning and a mandatory pre-release checklist. ## Core Features & Use Cases - Branch Management: Creates feature/<name> or fix/<name> branches from the latest main and pushes them to origin, never working directly on protected branches. - Semantic Version Tagging: Automatically computes the next MAJOR, MINOR, or PATCH version from the latest git tag, creates an annotated tag, and pushes it to the remote. - Single Source of Truth Alignment: Ensures package.json, index.html, and README.md version strings match the target git tag before release. - Use Case: After merging a new gameplay system, ask the agent to cut a minor release; it validates the checklist, bumps v1.2.3 to v1.3.0, tags it, and pushes to origin. ## Quick Start Create a minor release tag with release notes describing the new feature and push it to origin.

Frequently Asked Questions about git-release-management

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

FAQPage Schema
How do I create a semantic version git tag automatically?▼

Run the release operation with an increment type of major, minor, or patch. The Skill fetches the latest tag with git describe, increments the appropriate SemVer digit, creates an annotated tag, and pushes it to origin.

How to create a feature branch from the latest main in git?▼

Provide a branch name like feature/audio-system. The Skill checks out main, pulls the latest state from origin, creates the new branch, and pushes it upstream with git push -u.

What is the difference between major, minor, and patch version bumps?▼

Major increments for breaking changes or significant public releases, minor for new functionality and resets patch to zero, and patch for backward-compatible bug fixes, optimizations, or documentation updates.

Can I push commits directly to the main branch?▼

No. The Skill prohibits working directly on main or origin/main. All work must occur on feature/<name> or fix/<name> branches, with a declared release type before opening a merge request.

Why must package.json and README.md versions match the git tag?▼

The git tag is the single source of truth for versioning. Static files like package.json, index.html, and README.md must be updated to the exact target version before tagging to prevent inconsistent version reporting across the project.

Related Skills

Explore More Software Engineering Skills→
minhhhminhhh

finishing-a-development-branch

Verify feature branch tests pass before offering four finalization options.

Community
Advanced
mycelium-iomycelium-io
112

release

Automate software releases by tagging versions and publishing GitHub releases.

Official
Advanced
AbildtoftAbildtoft
2

kramme:verify

Run formatting, linting, type-checking, builds, and tests on affected code.

Community
Intermediate
marquesfelipmarquesfelip

automated-versioning

Automate semantic version bumps from conventional commits in CI/CD pipelines.

Community
Advanced