release

Automate GitHub release cutting with semantic versioning from Conventional Commits.

1|Updated May 8, 2026
One-click install
npx skills add https://github.com/paulnsorensen/skillz-that-grillz --skill release-paulnsorensen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/paulnsorensen/skillz-that-grillz/tree/main/skills/release
Command: npx skills add https://github.com/paulnsorensen/skillz-that-grillz --skill release-paulnsorensen

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

This skill turns a messy “we shipped changes—what version is next?” moment into a consistent, safe GitHub release process with correct semantic versioning and reader-ready release notes.

Core Features & Use Cases

  • Version decision from Conventional Commits: Determines the next semantic version by scanning non-merge commits since the last tag and selecting the highest-impact bump, including prerelease behavior.
  • Release notes drafting: Produces GitHub release notes using either auto-generated notes (via the release workflow config) or curated notes (grouped by change type), with optional highlights and upgrade notes for breaking changes.
  • Tagging and publishing ceremony: Creates and pushes an annotated tag, then publishes the GitHub release (or defers to a tag-driven workflow if present), followed by verification and a clear report of what happened.

Quick Start

Run the /release skill when your work is merged to the default branch to compute the next version, draft the notes, tag the commit, and publish the GitHub release.

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 from Conventional Commits?

Automate GitHub releases by scanning Conventional Commits since the last tag to compute the next semantic version. The skill then drafts release notes, pushes an annotated tag, and publishes the GitHub release.

How does semantic versioning get calculated from commit history?

Semantic versioning is calculated by scanning non-merge commits since the last tag. The skill selects the highest-impact change bump from your Conventional Commits history, including support for prerelease behaviors and existing tag conventions.

Can I generate release notes and update a CHANGELOG.md automatically?

Yes, you can generate GitHub release notes using auto-generated configurations or curated notes grouped by change type. The skill provides optional CHANGELOG.md updates and highlights upgrade notes for breaking changes.

What happens if my repository has a tag-driven release workflow?

If a tag-driven release workflow is present, the skill creates and pushes an annotated tag, then defers publishing to your existing workflow. It verifies the published release state via gh release view and reports the final outcome.

Does the release process work on branches with uncommitted changes?

No, the release process refuses to run on dirty or diverged repository states. It requires fetching tags and matching existing conventions to ensure a safe release ceremony after merges on the default branch.