release

Automate GitHub releases with versioning and changelog generation from pull requests.

3|4|Updated Apr 4, 2026
One-click install
npx skills add https://github.com/hmcts/agentic-plugins-marketplace --skill release-hmcts
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release
Source: https://github.com/hmcts/agentic-plugins-marketplace/tree/main/plugins/agents/hmcts-apim-sdlc-orchestrator/skills/release
Command: npx skills add https://github.com/hmcts/agentic-plugins-marketplace --skill release-hmcts

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires github, and includes scripts (resource) components.

What problem does it solve?

Manually cutting a new GitHub release for an API Management (APIM) service is a time-consuming and error-prone task. This skill automates the process of finding the latest changes, calculating the next version number, and generating a release with a changelog.

Core Features & Use Cases

  • Automated Release Versioning: Calculates the next release version based on the last tag and the most recent changes.
  • Release Note Generation: Extracts PR descriptions and categorizes them into new features, bug fixes, and improvements for the changelog.
  • User Confirmation: Confirms with the user before creating the release to prevent unintended actions.

Quick Start

Invoke the skill by running the command /release when you're ready to cut a new release for your APIM service.

Frequently Asked Questions about release

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

FAQPage Schema
How do I automate GitHub release versioning and changelog generation from pull requests?

Automated GitHub release versioning determines the next version number by analyzing the latest tag and recent pull request changes, then generates a categorized changelog. It requires GitHub API access to read repository information and PR details to compile the release notes.

How does automated changelog generation categorize pull request descriptions into release notes?

Changelog generation categorizes extracted pull request descriptions into new features, bug fixes, and improvements. By reading repository information and PR details through the GitHub API, it compiles these categorized changes directly into the release notes for the new version.

Do I need GitHub API access to calculate the next release version for my API Management service?

Yes, GitHub API access is required to calculate the next release version. The automation script reads repository information and PR details through the GitHub API to identify the latest changes and determine the appropriate version bump from the last tag.

What is the best way to prevent unintended automated GitHub releases in a CI/CD pipeline?

To prevent unintended automated GitHub releases, the process includes a user confirmation step before creating the release. After calculating the next version and generating the changelog, it prompts the user to verify and approve the action before publishing.

Can I use this release automation tool for API Management services without manual version tracking?

Yes, you can automate release versioning for API Management services without manual version tracking. The script calculates the next version automatically based on the last repository tag and collects changes from recent pull requests to generate the release.

Why does my automated GitHub release fail to collect recent pull request changes?

Automated GitHub release collection fails when the script lacks sufficient GitHub API permissions to read repository information and PR details. Proper API access is required to extract pull request descriptions and categorize them into the changelog for the release.