skills.rest
nullhack
nullhackCOMMUNITY
Explore all skills by this author →
GitHub

git-release

Automate tagged GitHub releases with major.minor.calver versioning.

Updated Apr 17, 2026
Search Tags:#automation#git#versioning#github#release-management#calver
One-click install
npx skills add https://github.com/nullhack/pytest-beehave --skill git-release-nullhack
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: git-release
Source: https://github.com/nullhack/pytest-beehave/tree/main/.opencode/skills/git-release
Command: npx skills add https://github.com/nullhack/pytest-beehave --skill git-release-nullhack

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Releasing software often suffers from inconsistent versioning, manual tagging, and misalignment between feature readiness and deployment. This skill automates the release workflow to ensure predictable, auditable releases.

Core Features & Use Cases

  • Hybrid versioning: uses major.minor.calver to encode breaking changes, feature additions, and daily releases.
  • AI-generated release names: assigns a unique adjective-bee genus name to every release for easy reference.
  • End-to-end release process: validates changes, creates a tagged GitHub release, updates changelog, and prepares release notes for stakeholders.
  • Governance and auditing: records release metadata for traceability and ensures consistency across environments.

Quick Start

Trigger the release workflow to publish a tagged GitHub release after a feature is accepted.

Frequently Asked Questions about git-release

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

FAQPage Schema
How do I automate GitHub release tagging for feature branches?▼

Automate GitHub release tagging by triggering a workflow that validates changes, creates a tagged release, updates the changelog, and prepares stakeholder release notes. This ensures consistent naming across feature-branch deployments.

What is hybrid major.minor.calver versioning and when do I need it?▼

Hybrid major.minor.calver versioning encodes breaking changes, feature additions, and daily releases into a single format. You need this when software teams require predictable, auditable release cycles across frequent deployments.

How do I ensure consistent release naming across multiple software environments?▼

Ensure consistent release naming by assigning a unique AI-generated adjective-bee genus name to every tagged release. This governance records release metadata for traceability across environments.

Can I integrate automated release management with a living-docs workflow?▼

Automated release management integrates with a living-docs workflow by validating changes and updating the changelog during the tagged GitHub release creation. This keeps documentation aligned with feature readiness.

What is the best way to handle versioning for scheduled deployments and PR merges?▼

Handle versioning for scheduled deployments and PR merges by applying a hybrid major.minor.calver format during the automated release process. This enforces predictable versioning across all deployment types.

Related Skills

Explore More Software Engineering Skills→
taiga-Ktaiga-K
1

create-branch

Create GitFlow feature, release, and hotfix branches with validated naming.

Community
Intermediate
rcarmorcarmo
147

Tag-based releases

Automates GitHub releases for tags matching v* via a workflow file.

Community
Intermediate
cosmixcosmix
53

ci-cd

Design and automate CI/CD pipelines for GitHub Actions, GitLab CI, and Jenkins.

Community
Advanced
jMertajMerta
130

release-notes

Generate Markdown release notes from git history and merged PRs.

Community
Basic