version-release

Automate GitHub release notes and versioning by routing the correct release workflow based on PR titles and branch naming rules. This enforces strict CI compatibility constraints, computing PR refs and metrics directly from git history to prevent versioning mistakes.

The correct PR title format for a minor GitHub release requires exact parsing to satisfy strict CI compatibility constraints. The Skill enforces these formatting guardrails to route the workflow accurately and prevent release-note mistakes during the LobeHub version release process.

Generate accurate GitHub release notes by computing inputs directly from git history rather than memory. This ensures PR refs, metrics, and contributors are verifiable, preventing inaccuracies when drafting the GitHub Release for minor, patch, hotfix, or DB migration releases.

Yes, the release workflow routing supports hotfixes and DB migration releases. It applies branch and title-based trigger logic to select the correct patch paths, enforcing CI-driven tagging and GitHub Release creation to maintain strict versioning compatibility.

CI triggers fail when patch release branch naming rules and PR titles do not match exact formatting constraints. The Skill enforces strict git-derived verification of PR refs to prevent these mismatches and ensure correct workflow routing for GitHub releases.

Yes, you can prepare a minor release by creating the release branch from canary and drafting the PR title in the exact required format. The Skill then guides writing the GitHub Release notes using the provided release-note standard.