create-release

Create draft GitHub prereleases with semver-aligned tags and markdown release notes.

43|2|Updated Jan 25, 2024
One-click install
npx skills add https://github.com/glowingkitty/OpenMates --skill create-release-glowingkitty
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-release
Source: https://github.com/glowingkitty/OpenMates/tree/main/.agents/skills/create-release
Command: npx skills add https://github.com/glowingkitty/OpenMates --skill create-release-glowingkitty

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you create consistent GitHub release drafts with correct semantic versioning and readable release notes instead of manually guessing tags and changelogs.

Core Features & Use Cases

  • Version determination for pre-releases: Chooses major/minor/patch bumps based on change type for v0.x.x-alpha workflows.
  • User-friendly release notes generation: Structures notes into sections for users and contributors rather than dumping raw commits.
  • GitHub release draft automation: Creates a prerelease draft targeting main, marked as a draft until you publish after merge.

Quick Start

Create a draft release by asking the AI to run the create-release workflow for the requested tag when your PR is ready to produce release notes.

Frequently Asked Questions about create-release

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

FAQPage Schema
How do I draft a GitHub release with correct semantic versioning for prereleases?

GitHub release draft automation creates a prerelease draft targeting main by determining the semver bump type, collecting recent tags, and applying contributor-friendly markdown release notes through the GitHub CLI.

How are release notes generated from recent git tags for a prerelease?

Release notes generation structures recent tags into human-readable markdown sections for users and contributors, categorizing new features, fixes, and breaking changes rather than dumping raw commits into the draft.

What is the best way to automate semantic version bumps for a PR workflow?

Automating semantic version bumps for a PR workflow involves evaluating change types to apply major, minor, or patch increments, ensuring consistent versioning across new features, fixes, and breaking changes before drafting the release.

Can I create a prerelease draft targeting the main branch using GitHub CLI?

Yes, you can create a prerelease draft targeting main using the GitHub CLI by collecting recent tags, applying semver-aligned prerelease tagging, and marking the release as a draft until you publish after merge.

Does this release drafting workflow support alpha v0.x.x versioning?

Yes, this release drafting workflow explicitly supports alpha v0.x.x versioning workflows by aligning prerelease tagging with semantic versioning rules tailored for early-stage development cycles.