version-release

Route GitHub minor and patch release workflows with release-note rules.

1|Updated May 9, 2026
One-click install
npx skills add https://github.com/duwenji/generative-ai-oss-tutorials --skill version-release-duwenji
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-release
Source: https://github.com/duwenji/generative-ai-oss-tutorials/tree/main/sandbox/lobe-chat/.agents/skills/version-release
Command: npx skills add https://github.com/duwenji/generative-ai-oss-tutorials --skill version-release-duwenji

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill reduces mistakes in release operations by routing the user to the correct, validated release-note and workflow steps for publishing versions on GitHub.

Core Features & Use Cases

  • Release workflow routing: Directs requests to the appropriate process for minor releases (exact semver in the PR title), patch releases (auto +1 triggers from branch/title patterns), and post-merge tagging and sync.
  • Correct release-note production: Ensures release notes follow the required style and hard rules by loading the referenced step-by-step guidance for computing inputs from git and verifying PR refs.
  • Scope protection: Prevents misuse by explicitly excluding website changelog generation and instead requiring the mandatory companion skill for microcopy.
  • Example use case: When you need to ship a weekly hotfix from main, you can follow the patch-release scenarios and generate release notes that cite only merged PR refs derived from git.

Quick Start

Use the version-release skill to generate correct GitHub Release notes by following the referenced minor or patch workflow for your targeted release type, ensuring all PR references are computed from git.

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 notes for semantic versioning in a CI workflow?

GitHub release notes automation routes minor and patch semantic versioning scenarios through CI workflows, enforcing release-note rules and computing PR references directly from git to generate accurate, validated outputs.

What is the difference between minor and patch release workflows for semantic versioning?

Semantic versioning minor releases require exact semver in the PR title, while patch releases trigger automatically from branch or title patterns, routing each to distinct post-merge tagging and GitHub Release note generation steps.

How to generate GitHub release notes from merged PR references using git?

Generating GitHub release notes from merged PRs involves loading referenced step-by-step guidance to compute PR references directly from git history, ensuring notes cite only verified, merged pull request refs.

Can I use this release workflow routing to generate website changelogs?

Release workflow routing explicitly excludes website changelog generation to enforce scope protection, requiring a mandatory companion microcopy skill for any changelog or microcopy execution tasks.

Do I need a companion skill for microcopy when shipping a patch release?

A companion microcopy skill is mandatory for patch releases because the version-release skill restricts its scope to CI trigger constraints, version detection, and GitHub Release note writing, delegating microcopy execution externally.

Why does my patch release workflow require auto increment triggers from branch patterns?

Patch release workflows require auto +1 triggers from branch or title patterns to correctly route semantic versioning operations, ensuring accurate version detection and post-merge tagging without manual version input.