version-release

Automates GitHub version releases via PR titles and branch names.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the complex and error-prone process of releasing software versions, ensuring consistency and reducing manual effort.

Core Features & Use Cases

  • Automated Version Bumping: Handles minor and patch version increments automatically.
  • Release Workflow Management: Guides through Minor and Patch release procedures.
  • CI/CD Integration: Triggers releases based on PR titles and branch names, creating tags and GitHub Releases.
  • Use Case: When you need to deploy a new feature or a hotfix, this skill ensures the correct versioning, tagging, and release notes are generated automatically.

Quick Start

Use the version-release skill to start a minor release by creating a release branch from canary.

Frequently Asked Questions about version-release

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

FAQPage Schema
How do I automate version bumping and GitHub release creation in my CI/CD pipeline?

Automated version bumping and GitHub release creation within a CI/CD pipeline is handled by triggering workflows based on predefined branch naming conventions and PR title formats. This ensures correct versioning, tagging, and reliable deployments automatically.

How does branch naming convention trigger a minor or patch release workflow?

Branch naming convention triggers a minor or patch release workflow by matching predefined formats in your CI/CD pipeline. Minor release procedures start by creating a release branch from canary, while patch releases handle hotfix version increments automatically.

What is the best way to streamline a software release process without manual versioning errors?

Streamlining a software release process without manual versioning errors requires automating minor and patch version increments, tagging, and GitHub release creation. Integrating these steps into CI/CD pipelines ensures consistent, reliable deployments and automated release notes.

Does this release workflow automation work with GitHub Actions for deployment?

Release workflow automation works seamlessly with GitHub Actions by integrating into your CI/CD pipelines. It triggers releases based on PR titles and branch names, automatically generating tags and GitHub Releases for consistent deployments.

Can I use PR title formats to manage minor and patch version increments automatically?

You can use PR title formats to manage minor and patch version increments automatically. The workflow automation parses predefined PR titles to determine the correct version bumping strategy and triggers the corresponding GitHub release creation.