skills.rest
pacaplan
pacaplanCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

release

Create release pull requests with semantic version bumps and changelog entries.

30|1|Updated Feb 18, 2026
Search Tags:#automation#changelog#versioning#github actions#release#pr
One-click install
npx skills add https://github.com/pacaplan/flokay --skill release-pacaplan
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/pacaplan/flokay/tree/main/.claude/skills/release
Command: npx skills add https://github.com/pacaplan/flokay --skill release-pacaplan

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of release pull requests, streamlining the process of preparing and publishing new versions of your software.

Core Features & Use Cases

  • Automated Version Bumping: Calculates semantic version bumps based on conventional commit messages.
  • Changelog Generation: Compiles changelog entries from merged pull requests.
  • Release PR Creation: Opens a pull request for the new release, ready for review and merging.
  • Use Case: After merging several features and fixes, you can trigger this Skill to automatically prepare a new release, including updating the version number, generating a changelog, and creating a PR.

Quick Start

Use the release skill to prepare a new release.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate release PRs and changelog generation?▼

Automating release PRs and changelog generation involves gathering merged pull requests since the last tag, calculating semantic version bumps from conventional commit titles, and opening a structured release pull request.

How does conventional commit versioning work for automated releases?▼

Conventional commit versioning for automated releases works by parsing merged pull request titles to calculate semantic version bumps, ensuring that features, fixes, or breaking changes correctly increment the version number.

How do I generate a changelog from merged pull requests?▼

To generate a changelog from merged pull requests, the system gathers all merged PRs since the last tag and compiles their commit messages into structured changelog entries for the new release.

Do I need GitHub Actions and jq to automate semantic version bumps?▼

You need the gh command-line tool and jq installed to automate semantic version bumps, as these dependencies are required to gather merged pull requests and parse JSON output for release PR creation.

What's the best way to prepare a software release after merging several features?▼

The best way to prepare a software release after merging features is to trigger an automation skill that calculates the semantic version bump, generates the changelog, and opens a release PR for review.

When should I not use an automated release PR workflow?▼

You should not use an automated release PR workflow if your project does not follow conventional commit message standards, as the semantic version bump calculation relies entirely on parsing commit titles.

Related Skills

Explore More Software Engineering Skills→
RoxabiRoxabi
9

release-setup

Configure commit standards and release automation tools for Node, Bun, Deno, or Python projects.

Official
Advanced
asklarasklar
24

release

Determine semantic versions, create Git tags, and push to trigger CI releases.

Community
Intermediate
richardadonnellrichardadonnell
45

semantic-versioning

Automate semantic versioning and changelog generation from conventional commits.

Community
Advanced
FaysilAlshareefFaysilAlshareef
4

changelog-gen

Generate changelogs from git commits using Conventional Commits and Keep a Changelog formats.

Community
Intermediate