skills.rest
me2resh
me2reshCOMMUNITY
Explore all skills by this author →
Website𝕏@me2reshGitHub

release

Cut an apexyard framework release with semver bump, CHANGELOG, and release PR.

489|254|Updated Apr 5, 2026
Search Tags:#changelog#git workflow#conventional commits#release#semver#tagging#github pull request
One-click install
npx skills add https://github.com/me2resh/apexyard --skill release-me2resh
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/release
Command: npx skills add https://github.com/me2resh/apexyard --skill release-me2resh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of turning a stream of changes on dev into a consistent, reviewable, production-ready release on main without manual semver mistakes, inconsistent changelogs, or premature tagging.

Core Features & Use Cases

  • Framework-only release flow: verifies the repo is the apexyard framework, enforces a dev→main model, and refuses to run on managed projects that use different governance.
  • Conventional-commit semver + changelog generation: auto-detects MAJOR/MINOR/PATCH from commit subjects, drafts a categorized CHANGELOG entry (including ticket-closing references), and lets you edit before opening the PR.
  • Release PR + post-merge tagging and required sync: opens a release PR (no auto-merge), tags and pushes only after merge, and mandates a main→dev sync PR to prevent accumulated squash divergence.

Quick Start

Run /release to auto-detect the semver bump from conventional commits, draft an editable CHANGELOG, and open the release PR from dev to main.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate semver bumps and changelog generation from conventional commits?▼

A PR-driven release workflow opens a release PR from dev to main, waits for merge review, and only applies git tagging and pushes afterward. It mandates a main-to-dev sync PR to prevent accumulated squash divergence.

How does a PR-driven git workflow handle tagging and branch syncing?▼

A PR-driven release workflow opens a release PR from dev to main, waits for merge review, and only applies git tagging and pushes afterward. It mandates a main-to-dev sync PR to prevent accumulated squash divergence.

Can I use this conventional commit release workflow for any GitHub repository?▼

You can run a release in dry-run mode to simulate the semver bump and changelog generation without opening a PR or making git changes. It also supports optional explicit version input to override the automatic semver detection.

Can I override the automatic version bump or run a release in dry-run mode?▼

You can run a release in dry-run mode to simulate the semver bump and changelog generation without opening a PR or making git changes. It also supports optional explicit version input to override the automatic semver detection.

Why does a release workflow refuse to run on certain repositories?▼

A release workflow refuses to run on invalid repo states or managed projects using different governance because it enforces strict framework-only preflight checks. This ensures the dev-to-main release cycle remains consistent and prevents incorrect tagging.

Related Skills

Explore More Software Engineering Skills→
AAbdulghanyAAbdulghany

release

Diff dev and main branches to determine SemVer bumps and generate CHANGELOG entries.

Community
Advanced
me2reshme2resh
489

release-sync

Create a main-to-dev PR with `-X ours` after a squash-merge release.

Community
Advanced
glowingkittyglowingkitty
43

create-pr

Create a pull request from dev to main using GitHub CLI.

Community
Intermediate
intelligentcode-aiintelligentcode-ai
35

release

Automates version bumps, changelog updates, PR merges, tagging, and GitHub releases.

Official
Advanced