release

Generate GitHub release commands from semantic versioning and changelog entries.

1|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/rubykachu/skill-scaffold --skill release-rubykachu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/rubykachu/skill-scaffold/tree/main/.cursor/skills/release
Command: npx skills add https://github.com/rubykachu/skill-scaffold --skill release-rubykachu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of GitHub releases, ensuring proper semantic versioning and generating release notes from your changelog, saving you time and reducing manual errors.

Core Features & Use Cases

  • Semantic Versioning: Enforces MAJOR.MINOR.PATCH versioning based on your SKILL.md file.
  • Automated Release Notes: Extracts relevant information from your CHANGELOG.md for release descriptions.
  • GitHub CLI Integration: Generates ready-to-run gh commands for creating releases, including options for assets, prereleases, and drafts.
  • Use Case: After merging significant changes and updating your CHANGELOG.md, you can use this Skill to quickly and accurately create a new GitHub release tag and description.

Quick Start

Use the release skill to create a new GitHub release for the current version.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate GitHub releases with semantic versioning?

You can automate GitHub releases by reading the version from SKILL.md and extracting notes from CHANGELOG.md to generate gh release create commands, ensuring proper semantic versioning.

What's the best way to generate release notes from a changelog for GitHub?

Generating release notes from a changelog involves extracting relevant entries from CHANGELOG.md and passing them into the gh release create command to populate the GitHub release description automatically.

Can I mark a GitHub release as a prerelease or draft using automation?

Yes, GitHub release automation can generate gh release create commands with specific flags to mark the release as a prerelease or draft, alongside standard options for adding binary assets.

Does this release automation require the GitHub CLI to create tags?

Yes, GitHub release automation relies on the GitHub CLI to execute the generated gh release create commands, which handle both tag creation and publishing the extracted changelog notes.

Why does my automated GitHub release fail when the tag already exists?

Automated GitHub releases fail when a tag already exists because the gh release create command conflicts with existing tags; the process includes error handling to catch this and authentication issues.

How do I enforce MAJOR.MINOR.PATCH versioning for my GitHub releases?

To enforce MAJOR.MINOR.PATCH semantic versioning, the automation reads the designated version string directly from the SKILL.md frontmatter to ensure the GitHub release tag matches your defined version.