release

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

Updated Apr 15, 2026
One-click install
npx skills add https://github.com/AAbdulghany/fms --skill release-aabdulghany
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/AAbdulghany/fms/tree/main/.claude/skills/release
Command: npx skills add https://github.com/AAbdulghany/fms --skill release-aabdulghany

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Release automation for apexyard projects, standardizing the dev→main flow and eliminating manual release toil.

Core Features & Use Cases

  • Auto-detects semver bumps from conventional commits between dev and main.
  • Generates a CHANGELOG entry and opens a release PR.
  • Tags the release on merge and pushes the tag to the remote repository; supports optional explicit version.
  • Works in multi-branch workflows and enforces pre-flight validations to ensure a safe release.

Quick Start

Trigger a release with /release to auto-detect the next version, generate the CHANGELOG, open the release PR, and tag after merge.

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?

The release workflow diffs dev and main branches to auto-detect the correct SemVer bump from conventional commits, generates a matching CHANGELOG entry, and opens a release PR to standardize the process.

What's the best way to automate a dev to main release workflow with pull requests?

The best way to automate a dev to main release workflow is to enforce pre-flight checks for branch presence and commit history, open a release PR, and automatically tag the release on merge to eliminate manual toil.

How do I tag a release and push it to a remote Git repository after a PR merge?

To tag a release after a PR merge, the workflow waits for approval, tags the merged commit, and pushes the tag to the remote Git repository to finalize the version deployment automatically.

Does the release automation enforce pre-flight checks before opening a pull request?

Yes, the release automation enforces pre-flight checks before opening a pull request to verify framework eligibility, branch presence, and commit history, ensuring a safe release in multi-branch workflows.

Can I specify an explicit version instead of auto-detecting the SemVer bump?

Yes, you can specify an explicit version instead of relying on auto-detection from conventional commits, overriding the calculated SemVer bump to force a specific release number.