github-release

Automates GitHub releases by staging files, committing, tagging, and creating releases via gh CLI.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/Pgooone/oh-pgone-claudecode --skill github-release-pgooone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-release
Source: https://github.com/Pgooone/oh-pgone-claudecode/tree/main/.claude/skill/github-release
Command: npx skills add https://github.com/Pgooone/oh-pgone-claudecode --skill github-release-pgooone

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Publishing a new version to GitHub involves many error-prone manual steps: checking tool availability, staging the right files, writing a proper commit message, pushing, tagging, and drafting release notes. This Skill standardizes the entire release workflow so nothing is forgotten and no sensitive files are accidentally committed. ## Core Features & Use Cases - Pre-flight Dependency Checks: Verifies git, GitHub CLI (gh), authentication status, and repository context before starting, with platform-specific install guidance. - Safe Staging and Committing: Stages files individually (never git add .) and writes structured Chinese commit messages following a version-prefixed format. - Tag and Release Creation: Pushes semver tags and generates a formatted GitHub Release with changelog links via gh release create. - Use Case: After finishing a feature branch, ask the assistant to publish v0.2.0 — it checks your environment, commits the changed files, pushes, tags, and creates the Release with notes in one guided flow. ## Quick Start Use the github-release skill to publish version v0.2.0 of this repository to GitHub with release notes.

Frequently Asked Questions about github-release

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

FAQPage Schema
How do I create a GitHub release from the command line?▼

Use the GitHub CLI command gh release create with a version tag, title, and notes. This Skill automates the full sequence: staging files, committing, pushing, tagging with semver, and running gh release create with formatted notes.

How to tag and push a release version with git?▼

Create a semver tag with git tag v0.1.1, then push it using git push origin v0.1.1. The Skill first checks that the tag does not already exist with git tag -l before creating it.

What tools are required to publish a GitHub release?▼

You need git and the GitHub CLI (gh) installed, plus an authenticated gh session via gh auth login. The included check-tools.sh script verifies all dependencies and prints platform-specific install instructions if anything is missing.

Why should I avoid git add . when committing a release?▼

Using git add . can accidentally stage sensitive files like .env or credentials. This Skill stages files individually by path and confirms with git status before committing, reducing the risk of leaking secrets.

What commit message format does this release workflow use?▼

Commits use a Chinese-language format: version number, short description, a bulleted list of changes, and a Co-Authored-By trailer. The version number must match the git tag, as documented in the commit-format reference.