release

Automate GitHub releases with SemVer versions and commit-based notes.

6|2|Updated Jan 26, 2026

Search Tags:#automation #devops #versioning #github #release #semver

Ready to run

npx skills add https://github.com/freepik-company/knowledge-agent --skill release-freepik-company

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release
Source: https://github.com/freepik-company/knowledge-agent/tree/main/.claude/skills/release
Command: npx skills add https://github.com/freepik-company/knowledge-agent --skill release-freepik-company

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the complex and error-prone process of creating professional releases on GitHub, ensuring consistency and safety.

Core Features & Use Cases

Automated Versioning: Determines the correct SemVer version (major, minor, patch) based on commit history or explicit input.
Intelligent Release Notes: Generates clear, categorized release notes by summarizing relevant commits.
Risk Assessment: Flags potential breaking changes and necessary post-release actions.
Use Case: After merging a new feature and several bug fixes, use this Skill to automatically determine the next version number, draft release notes, and generate the gh release create command for review.

Quick Start

Use the release skill to create a patch release based on the latest commits.

Frequently Asked Questions about release

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

FAQPage Schema

How do I automate GitHub releases using commit history?▼

Automate GitHub releases by analyzing commit history to determine SemVer version bumps, generate categorized release notes, and output a ready-to-run gh release create command. This ensures consistent versioning without manual calculations.

How does SemVer version bumping work for patch, minor, and major changes?▼

SemVer version bumping evaluates commit history to automatically determine whether a patch, minor, or major version increment is needed. It identifies breaking changes for major bumps and new features for minor bumps, ensuring accurate semantic versioning.

Can I generate draft release notes from commit history before publishing?▼

Yes, you can generate draft release notes from commit history. The process summarizes relevant commits into categorized release notes, flags breaking changes, and provides a draft command for review before executing the actual GitHub release.

Do I need the GitHub CLI to create draft releases?▼

Yes, the GitHub CLI is required to create draft releases. The process generates a ready-to-run gh release create command that you review and execute, ensuring safe and controlled release publishing directly from your environment.

What is the best way to identify breaking changes before a GitHub release?▼

The best way to identify breaking changes is through automated risk assessment of commit history. The process flags potential breaking changes and highlights necessary post-release actions, preventing unexpected disruptions in your versioning workflow.