skills.rest
Emmanuelkwaa
EmmanuelkwaaCOMMUNITY
Explore all skills by this author →
GitHub

create-release

Create GitHub releases with auto-generated notes from commit history.

1|Updated Mar 9, 2026
Search Tags:#automation#git#versioning#deployment#github#release
One-click install
npx skills add https://github.com/Emmanuelkwaa/NetRockTemplate --skill create-release-emmanuelkwaa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-release
Source: https://github.com/Emmanuelkwaa/NetRockTemplate/tree/main/.claude/skills/create-release
Command: npx skills add https://github.com/Emmanuelkwaa/NetRockTemplate --skill create-release-emmanuelkwaa

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of creating GitHub releases, including generating release notes based on commit history and ensuring proper versioning.

Core Features & Use Cases

  • Automated Release Creation: Creates GitHub releases with auto-generated notes.
  • Semantic Versioning Enforcement: Adheres to major, minor, and patch versioning.
  • Commit Analysis: Categorizes changes (features, fixes, etc.) for release notes.
  • Use Case: After merging several feature branches and bug fixes into master, use this Skill to create a new patch release on GitHub with accurate release notes.

Quick Start

Use the create-release skill to create a patch release from the master branch.

Frequently Asked Questions about create-release

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

FAQPage Schema
How do I automate GitHub releases based on commit history?▼

You can automate GitHub releases by categorizing commit history into features, security, bug fixes, and infrastructure changes. This skill generates release notes, enforces semantic versioning, signs tags, and publishes from the master branch using GitHub CLI.

Do I need GitHub CLI to create semantic versioning tags?▼

Yes, you need both git and GitHub CLI installed. These tools are required for local tag creation, signing, pushing tags to the remote repository, and publishing the final automated release to GitHub.

Can I generate release notes from a branch other than master?▼

No, this skill enforces releasing strictly from the master branch. You must merge your feature branches and bug fixes into master before initiating the automated release creation and tag signing process.

How does semantic versioning categorize commit history for release notes?▼

Semantic versioning categorizes commit history by grouping changes into features, security, bug fixes, improvements, documentation, and infrastructure. This categorization automatically generates structured and accurate release notes for each GitHub release.

What is the best way to create a patch release with signed git tags?▼

The best way to create a patch release with signed git tags is using an automated skill that enforces semantic versioning. It analyzes your commit history, signs the git tags, and pushes them to GitHub alongside categorized release notes.

Related Skills

Explore More Software Engineering Skills→
kirvinkirvin

release

Automate versioned software releases with semantic versioning and GitHub CLI.

Community
Advanced
Sharper-FlowSharper-Flow
4

adv-ci-release

Automate release lifecycle with semver versioning and GitHub releases.

Official
Advanced
rnavarychrnavarych
14

git-workflows

Guide Git branching, commit conventions, and pull request workflows.

Community
Intermediate
cartridge-ggcartridge-gg
80

dispatch-release

Dispatch release preparation PRs and publish to npm and GitHub Releases.

Official
Advanced