github-release

Automate semantic versioned GitHub releases with changelog PRs.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/selfagency/agentsy --skill github-release-selfagency
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-release
Source: https://github.com/selfagency/agentsy/tree/main/.agents/skills/github-release
Command: npx skills add https://github.com/selfagency/agentsy --skill github-release-selfagency

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill removes the guesswork and busywork of cutting a new GitHub library release by guiding version discovery, change analysis, SemVer bump selection, changelog creation, and release PR setup.

Core Features & Use Cases

  • End-to-end GitHub release workflow: Determines the latest version tag, analyzes diffs, proposes the next SemVer version, and prepares the release branch and PR.
  • SemVer-aware change classification: Infers MAJOR/MINOR/PATCH from public API changes (added/removed/changed) and reconciles code diffs with commit-message intent.
  • Keep a Changelog formatting automation: Generates a properly structured changelog section (Added/Changed/Removed/Fixed/Security) and updates comparison links.

Quick Start

Use the github-release skill to propose a version bump and open a release PR for your repository using your latest tags and public-facing source changes.

Frequently Asked Questions about github-release

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

FAQPage Schema
How do I automate a GitHub release workflow with semantic versioning?

Automate a GitHub release workflow by analyzing git tags, diffing public source changes, and proposing a SemVer version bump to prepare the release branch and PR.

Can I automatically generate a Keep a Changelog formatted section for a new library version?

Yes, generate a Keep a Changelog formatted section by inferring Added, Changed, Removed, Fixed, and Security entries from source code diffs and updating comparison links.

How does SemVer change classification work when preparing a release PR?

SemVer change classification infers MAJOR, MINOR, or PATCH bumps by analyzing public API changes and reconciling code diffs with commit-message intent.

Do I need the GitHub CLI installed to create release branches and open PRs?

Yes, you need an authenticated GitHub CLI environment because the workflow uses only gh and git commands to read tags, compute diffs, create branches, and open the release PR.

What is the best way to determine the next version tag for my repository?

Determine the next version tag by analyzing existing git tags and calculating source code diffs to propose the appropriate semantic version bump for the release.

Are there limitations when using git and gh cli for release automation?

Release automation is limited to environments with authenticated GitHub CLI access and relies entirely on git and gh commands to read tags, compute diffs, and open PRs.