Agent skill · Documentation

github-release

Guides IA through releasing a new version of a GitHub library end-to-end. Handles SemVer versioning and Keep a Changelog formatting automatically.

GitHub68,948★ · +463/wk · 2 repos on radarProfile →
copilotMIT
Install
npx skills add github/awesome-copilot --skill github-release --agent copilot

Same command for any agent — swap --agent for claude-code, codex, cursor.

Facts
Files in the skill folder: 3
SKILL.md size: 14 KB
Bundled scripts: none
Requires: requires: gh CLI and git
Path: skills/github-release/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 37,432 · +281 this week
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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: ```bash 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: > *"Which directory contains your library's public-facing source code? >

What's inside
Steps it walks through
  1. When to Use This Skill
  2. Prerequisites
  3. The 9-Step Release Workflow
  4. Step 1 - Ensure main is up to date
  5. Step 2 - Grab the latest version tag
  6. Step 3 - Analyse what changed since the last release
  7. Step 4 - Determine the next SemVer version
  8. Step 5 - Create the release branch
  9. Step 6 - Update CHANGELOG.md
  10. Step 7 - Commit and push
  11. Step 8 - Open a Pull Request
  12. Step 9 - Hand off to the user
  13. Error handling
  14. Troubleshooting in PowerShell
Ships with 2 files
  • references/commit-classification.md
  • references/semver-rules.md
Commands it runs
gh auth status                        # must be authenticated
gh repo view --json nameWithOwner     # must be inside a GitHub repo
git status                            # working tree should be clean
git checkout main
git pull origin main
Fetch all tags from remote to ensure local view is current
git fetch --tags
Find the latest version tag, sorted semantically
echo "Latest tag: $PREV_TAG"
git ls-remote --tags origin | grep "refs/tags/$PREV_TAG$"
More from awesome-copilot
All skills →
About this skill
What does the github-release skill do?

Guides IA through releasing a new version of a GitHub library end-to-end. Handles SemVer versioning and Keep a Changelog formatting automatically.

How do I install it?

Run `npx skills add github/awesome-copilot --skill github-release --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going