gh-release

name	gh-release
description	Create GitHub Release with auto-generated release notes. Use when creating GitHub releases. Triggers on "release", "發布", "gh-release", "/gh-release", "建立 release".
allowed-tools	Bash, Read, Grep
version	1.0.0
scope	public
evolution	{"enabled":true,"version":"1.0.0","stability":"stable","auto_evolve":"patch","created":"2026-02-17T00:00:00.000Z","updated":"2026-02-17T00:00:00.000Z","history":[{"version":"1.0.0","date":"2026-02-17","note":"Initial version"}]}

GH Release

Create a GitHub Release with auto-generated release notes from git log.

---

Integrations

upstream:
  - skill: gh-tag
    receives: Created git tag
  - skill: gh-push
    receives: Tag pushed to remote

downstream:
  - output: GitHub Release
    produces: Publicly visible release page

---

Out of Scope

• Tagging - Use gh-tag
• Push - Use gh-push
• Uploading build artifacts - Handled by CI automatically
• Draft release - Creates official release directly

---

When to Use

• Tag has been created and pushed to remote
• Need to create a GitHub Release
• User requests publishing a version

---

Workflow

Phase 1: Check Prerequisites

1. Confirm tag exists and has been pushed

   git tag -l "v*" | sort -V | tail -3
   git ls-remote --tags origin | grep "v{version}"
   

   • If tag does not exist, prompt to use gh-tag
   • If tag has not been pushed, prompt to use gh-push

2. Confirm release has not been created yet

   gh release list --limit 5
   

   • If release already exists, notify the user and stop

3. Find previous tag

   git tag -l "v*" | sort -V | tail -2 | head -1
   

Phase 2: Generate Release Notes

4. Get commit history

   git log {prev_tag}..{tag} --oneline
   

5. Categorize commits to generate notes

   Categorize by Conventional Commits type:

   Type	Section Title
   feat	What's New
   fix	Bug Fixes
   perf	Performance
   refactor, style	Improvements
   docs	Documentation
   chore, ci, build	Other Changes

   Each section uses a bullet list, one line per commit, using the subject part. Empty sections are omitted.

6. Add Full Changelog link

   ## Full Changelog
   https://github.com/{owner}/{repo}/compare/{prev_tag}...{tag}
   

Phase 3: Create Release

7. Switch gh auth to the correct account

   Path	GH Account
   ~/work/	pdyei
   ~/personal/, ~/site/	panda850819

   gh auth status 2>&1 | grep "Active account: true" -B2 | head -1
   gh auth switch --user <expected-account>  # if needed
   

8. Create release

   gh release create {tag} \
     --title "{product} {tag}" \
     --notes "$(cat <<'EOF'
   {generated notes}
   EOF
   )"
   

   • {product} is obtained from package.json name, Cargo.toml package name, or repo name
   • Title format: {Product Name} {tag} (e.g. "Murmur Voice v0.3.0")

9. Display results

   • Release URL
   • If CI will automatically upload artifacts, notify the user to wait

---

Safety and Escalation

Situation	Action
Tag does not exist	Prompt to use gh-tag
Tag not pushed	Prompt to use gh-push
Release already exists	Notify user, do not overwrite
gh auth on wrong account	Switch automatically
No previous tag	Use --first-parent from the first commit
gh CLI not installed	Prompt to install

---

Verification

# Confirm release has been created
gh release view {tag}

# Confirm release list
gh release list --limit 3