Github Release

Automates the full GitHub release workflow from analysis through changelog generation to PR creation, using only the gh CLI and git. It reads your commit history and code diffs, figures out whether you need a major, minor, or patch bump according to SemVer, formats a changelog in Keep a Changelog style, and opens a release PR. The first four steps are read-only reconnaissance so you can review the proposed version before anything gets written. Honestly most useful if you maintain libraries and are tired of manually comparing diffs to SemVer rules or formatting changelogs by hand. It leans heavily on code diff analysis over commit messages, which is the right call since commits lie but deleted functions don't.

skills.sh installs: 790
GitHub stars: 41K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add github/awesome-copilot --skill github-release --agent claude-code

Installs into .claude/skills of the current project.

Files

GitHub Release Skill

This skill automates the full release workflow for a single-package GitHub repository, from analysis through changelog authoring and PR creation. It relies exclusively on gh (GitHub CLI) and git no other tools needed.

Steps 1 - 4 are read-only reconnaissance nothing is written to the repo until Step 5, once the version number is confirmed.

When to Use This Skill

Use this skill whenever the user wants to cut a new release, publish a new version, bump a version, create a release branch, generate a changelog, or open a release PR on a GitHub repository. Trigger even if the user says something casual like "let's ship a new version" or "time to release".

Prerequisites

Examples below include both Bash and PowerShell variants; Windows users should prefer the PowerShell blocks.

Before starting, verify the environment:

gh auth status                        # must be authenticated
gh repo view --json nameWithOwner     # must be inside a GitHub repo
git status                            # working tree should be clean

If any check fails, stop and tell the user what to fix before continuing.

Then ask the user one question:

SKILL.md on GitHub