version-release

Automate software releases with Git tags, GitHub Release APIs, and version bumping.

Updated Jul 8, 2026
One-click install
npx skills add https://github.com/alceupassos/hub --skill version-release-alceupassos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-release
Source: https://github.com/alceupassos/hub/tree/main/.agents/skills/version-release
Command: npx skills add https://github.com/alceupassos/hub --skill version-release-alceupassos

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill unit automates and orchestrates the entire software release workflow, including version bumping, creating GitHub Release notes, and post-release automation, eliminating the need for manual and error-prone release processes.

Core Features & Use Cases

  • Automated Versioning: Bumps versions in 'package.json' automatically after a merge into the main branch.
  • GitHub Release Automation: Creates GitHub Releases and tags, syncs with canary branches, and triggers other automated actions.
  • Customizable Workflow: Configurable to support minor, patch, hotfix, and model release types, each with specific workflow configurations.
  • Companion Skills Integration: Requires 'microcopy' for text handling and 'release-notes-style' for release note standards.
  • Use Case: Integrate this Skill into your CI/CD pipeline for a fully automated and consistent software release process, enhancing both productivity and code quality.

Quick Start

Run the skill using the 'version-release' command, and provide either a minor or patch release number to initiate the workflow.

Frequently Asked Questions about version-release

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

FAQPage Schema
How do I automate GitHub release creation and version bumping after a PR merge?

Automated release management matches specific commit titles from PR merges into the main branch to trigger version bumping in package.json and create GitHub Releases and tags automatically.

What is the best way to manage software lifecycle releases using Git version tags?

Software lifecycle release management uses Git version tags and GitHub Release APIs to orchestrate version bumping, tag creation, and post-release automation, eliminating manual release processes.

Can I customize the release workflow for different types of updates like hotfixes or minor releases?

The release workflow is configurable to support minor, patch, hotfix, and model release types, each with specific workflow configurations matched to specific commit titles for release purposes.

How does CI/CD pipeline integration work with automated release management?

CI/CD pipeline integration automates the release workflow by triggering version bumps, creating GitHub Releases and tags, syncing canary branches, and initiating post-release automated actions.

Do I need companion skills to handle release notes and text formatting?

The release workflow requires companion skills: 'microcopy' for text handling and 'release-notes-style' for standardizing release note formats to ensure consistent outputs.

Are there limitations when triggering automated releases based on commit titles?

Automated triggering relies on matching specific commit titles from PR merges into the main branch; commits without matching titles will not initiate the version bump or release creation workflow.