release-finalizer

Name: release-finalizer
Availability: InStock
Author: Fu-Jie

Merge release PRs into main and close linked issues automatically.

286|24|Updated Dec 20, 2025

Search Tags:#automation #github #release #merge #pull-request #issue-closing

Ready to run

npx skills add https://github.com/Fu-Jie/openwebui-extensions --skill release-finalizer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: release-finalizer
Source: https://github.com/Fu-Jie/openwebui-extensions/tree/main/.gemini/skills/release-finalizer
Command: npx skills add https://github.com/Fu-Jie/openwebui-extensions --skill release-finalizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manually coordinating release PR merges and related issue closures is error-prone and time-consuming; this skill automates the end-to-end flow to ensure releases are merged swiftly with properly linked issues.

Core Features & Use Cases

Automates PR readiness checks (OPEN state, status checks passing, approvals) before merging.
Associates related issues via PR description or commits and closes them automatically upon merge.
Generates a conventional commits compliant merge message that references all linked issues.

Quick Start

Merge the release PR into main and close all related issues.

Frequently Asked Questions about release-finalizer

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

FAQPage Schema

How do I automatically merge a release pull request and close linked issues?▼

To automatically merge a release pull request and close linked issues, you can use a release automation skill that evaluates PR readiness, merges into main using a configured strategy like squash, and generates a conventional commits message that automatically closes associated GitHub issues.

What checks are required before automating a GitHub release PR merge?▼

Before automating a GitHub release PR merge, the pull request must be in an OPEN state, have passing status checks, and receive approved reviews to ensure the branch is fully validated and ready for integration into the main branch.

Can I configure the merge strategy for automating release PR merges?▼

Yes, you can configure the merge strategy for automating release PR merges. The default method is squash, but you can also specify rebase or standard merge to control how commits are integrated into the main branch.

How does a conventional commits merge message link to related GitHub issues?▼

A conventional commits merge message links to related GitHub issues by generating a compliant commit message that includes Closes keywords for all linked issues, ensuring they are automatically closed upon the release PR merge.

How are related GitHub issues associated with a release PR for automatic closure?▼

Related GitHub issues are associated with a release PR for automatic closure by detecting references within the PR description or commits, which are then aggregated into the merge message using Closes keywords.