git-publish-release

Generate GitHub Release Notes and publish releases from commit history.

47|8|Updated Jan 3, 2026
One-click install
npx skills add https://github.com/huangwb8/skills --skill git-publish-release
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: git-publish-release
Source: https://github.com/huangwb8/skills/tree/main/git-publish-release
Command: npx skills add https://github.com/huangwb8/skills --skill git-publish-release

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill automates the generation of professional GitHub Release Notes and the publishing of releases by analyzing commit history across tags, saving time and reducing manual errors.

Core Features & Use Cases

  • Automated Release Notes: AI-assisted generation of concise, value-focused release notes from commit history.
  • One-click Release: Create or update GitHub releases with the correct tag and release notes.
  • Prerelease Support: Automatically detect prerelease tags (alpha/beta/rc) and set prerelease status.

Quick Start

Ask the skill to publish a new release for a specific tag to GitHub.

Frequently Asked Questions about git-publish-release

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

FAQPage Schema
How do I automatically generate GitHub release notes from commit history?

Automated release notes generation analyzes commit history across tags to create concise summaries. It classifies changes by comparing tags, detecting repository owner and name from git remote to prepare the release notes.

Can I create a GitHub prerelease for alpha, beta, or rc tags?

Yes, prerelease support automatically detects alpha, beta, and rc tags. It sets the correct prerelease status on GitHub by identifying these specific version tags during the release publishing process.

How do I publish a GitHub release using a GH_TOKEN?

Publishing a GitHub release requires a GH_TOKEN to authenticate API calls. The automation reads the latest releases, classifies changes, and calls the GitHub API to create or update the release with the correct tag.

Does this release automation work for a project's first release?

Yes, the release automation applies to first releases as well as standard version updates. It handles tag comparison and release creation across any GitHub project, accommodating initial versioning scenarios.

What's the best way to manage git tags for CI/CD versioning?

Managing git tags for ci/cd versioning is handled by analyzing commit history across tags. It detects the repository owner and name from git remote to ensure accurate tag comparison and release creation.