github-release

Automates GitHub release creation with semver analysis and changelog generation.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/paulund/ai --skill github-release-paulund
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-release
Source: https://github.com/paulund/ai/tree/main/git/skills/github-release
Command: npx skills add https://github.com/paulund/ai --skill github-release-paulund

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) components.

What problem does it solve?

This Skill streamlines the process of publishing new GitHub releases, ensuring versioning consistency and generating user-friendly release notes.

Core Features & Use Cases

  • Automated Versioning: Automatically determines the next semantic version (semver) based on commit messages.
  • Release Note Generation: Creates customer-facing release notes by summarizing changes.
  • Use Case: After merging a new feature and several bug fixes into your main branch, use this Skill to automatically tag a new release, write clear release notes, and publish it to GitHub.

Quick Start

Use the github-release skill to publish a new version of the project.

Frequently Asked Questions about github-release

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

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

To automate GitHub releases with semantic versioning, this Skill fetches existing git tags, analyzes commit messages for semver compliance to determine the next version, generates release notes, and publishes the release directly to GitHub.

How are release notes generated from git commits?

Release notes are generated by analyzing commit messages to identify semantic versioning compliance, summarizing the changes into user-friendly release notes, and automatically tagging the repository to publish the finalized changelog to GitHub.

Do I need the gh CLI installed to automate version tagging?

Yes, you need both git and the gh CLI installed to automate version tagging, as the Skill relies on gh for direct publishing to GitHub repositories and git for fetching tags and managing version control.

What is the best way to determine the next semver version from commit history?

The best way to determine the next semver version from commit history is to analyze merged commits for semantic versioning compliance, automatically bumping the version tag based on the nature of the changes before publishing a new GitHub release.

Can I generate changelogs and publish them to GitHub automatically?

Yes, you can generate changelogs and publish them automatically by using this Skill to summarize commit changes into customer-facing release notes and pushing the result as a new release directly to your GitHub repository.

Why does my automated GitHub release fail to determine the correct semantic version?

Automated GitHub release semver determination fails when commit messages lack clear semantic versioning compliance, preventing the Skill from accurately analyzing the history to generate the correct next version tag and release notes.