version-release

Automate minor and patch release workflows with PR and tagging steps.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines and standardizes how software versions are released across canary and main branches, reducing manual steps and human error.

Core Features & Use Cases

  • Minor Release: plan, branch, and PR flow for feature-level releases.
  • Patch Release: weekly or hotfix patch management with automatic version bumps.
  • Use Case: When you need to publish a small update or a critical fix, follow this workflow to ensure consistent release tagging and changelog guidance.

Quick Start

Start a Minor Release workflow from the canary branch to prepare the version bump, PR, and tagging.

Frequently Asked Questions about version-release

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

FAQPage Schema
How do I automate a patch release workflow for a hotfix?

To automate a patch release workflow for a hotfix, this standardized process provides automatic version bumps and changelog guidance to ensure consistent release tagging from branch to production.

What is the best way to manage minor version releases across canary and main branches?

The best way to manage minor version releases is by applying a structured workflow that handles branching, PR formats, and version tagging across canary-to-main release cycles to reduce human error.

Can I use this version-release workflow for a weekly release train?

Yes, this version-release workflow explicitly supports weekly release trains, applying structured branch rules and PR formatting to standardize your ongoing software project updates.

Do I need any external dependencies to manage git tagging and changelog generation?

No external dependencies are required to manage git tagging and changelog generation, as this implementation delivers a self-contained structured process for your software project releases.

How does the canary-to-main release cycle work for software upgrades?

The canary-to-main release cycle works by applying a structured process with specific branch rules, PR formats, and tagging guidance to streamline version upgrades and reduce manual steps.