What is release-finalizer?

A release-closing workflow for merging a reviewed GitHub pull request and resolving its linked issues. GitHub issues are task or bug reports, and a pull request is a proposed code change awaiting review.

Use it when a release pull request is approved and all checks pass, to identify linked issues, reply with solutions, merge the pull request, and close those issues.

It checks that reviews and automated tests are complete before merging. It also helps finish the related issue reports instead of leaving them open after the fix is released.

release-finalizer — Skill for Claude Code and Codex by Fu-Jie

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add Fu-Jie/openwebui-extensions --skill release-finalizer

Clone the repo

git clone --depth 1 https://github.com/Fu-Jie/openwebui-extensions

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/fu-jie/openwebui-extensions/release-finalizer/github.svg)](https://agentmods.dev/skills/fu-jie/openwebui-extensions/release-finalizer)

Your own site

<a href="https://agentmods.dev/skills/fu-jie/openwebui-extensions/release-finalizer"><img src="https://agentmods.dev/badge/skills/fu-jie/openwebui-extensions/release-finalizer/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/fu-jie/openwebui-extensions/release-finalizer"><img src="https://agentmods.dev/badge/skills/fu-jie/openwebui-extensions/release-finalizer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,570 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00042	$0.01570
Opus 5.5	$0.00017	$0.00628
Sonnet 5.5	$0.00008	$0.00314
Haiku 4.5	$0.00004	$0.00157

Measured 1mo ago against content hash 8c85c9c4792c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

release-finalizer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agent/skills/release-finalizer/SKILL.md · 209 lines

How it starts

The opening of the file, as written. The whole thing — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Release Finalizer

Overview

This skill completes the final step of the release cycle: merging the release PR to main, replying to all related issues with solutions, and automatically closing them using GitHub's issue linking mechanism.

Prerequisites

The PR is in OPEN state and ready to merge
All status checks have passed (CI green)
All review feedback has been addressed
The PR relates to one or more GitHub issues (either in PR description or through commits)

Workflow

Step 1 — Pre-Merge Verification

Verify that the PR is ready:

PAGER=cat GH_PAGER=cat gh pr view <PR-NUMBER> --json state,statusCheckRollup,reviewDecision

Checklist:

✅ state is OPEN
✅ statusCheckRollup all have conclusion: SUCCESS
✅ reviewDecision is APPROVED or empty (no blocking reviews)

If any check fails, do NOT merge. Report the issue to the user.

Step 2 — Identify Related Issues

Issues can be linked to a PR in multiple ways. Check the PR description and commit messages for keywords:

PAGER=cat GH_PAGER=cat gh pr view <PR-NUMBER> --json body,commits

Look for patterns like:

Closes #XX, Fixes #XX, Resolves #XX (in description or commit bodies)
#XX mentioned as "related to" or "addresses"

Manual input: If issue links are not in the PR, ask the user which issue(s) this PR resolves.

Extract all issue numbers into a list: [#48, #52, ...]

Step 3 — Select Merge Strategy

Offer the user three options:

Strategy	Git Behavior	Use Case
Squash	All commits squashed into one commit on main	Clean history, recommended for release PRs
Rebase	Linear history, no merge commit	Preserve commit granularity
Merge	Merge commit created	Preserve full PR context

Recommendation for release PRs: Use --squash to create a single clean commit.

If user doesn't specify, default to --squash.

Step 4 — Prepare Merge Commit Message

Read the full file on GitHub · 209 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 209 lines · 42 tokens per session scan A 8c85c9c4792c

Subscribe to this mod's changes

release-finalizer is a skill published in the GitHub repository Fu-Jie/openwebui-extensions (327 stars, last pushed 11d ago), licensed MIT. It adds 42 tokens to every session and 1,570 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Git and workflow Memory and context Releases context-engineering excel infographic mindmap openwebui

gsd-complete-milestone

Archive completed milestone and prepare for next version.

open-gsd/gsd-core · 16 tokens

github-ops

GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.

fuyuxiang/echo-agent · 31 tokens

release

Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.

matrixorigin/memoria · 27 tokens

update

Safe cc10x upgrade through the Claude Code plugin CLI. Lists every installed scope, refreshes the marketplace, updates each scope, and optionally carries local patches over to the new install. Use this skill when: updating cc10x, upgrading, pulling latest cc10x, syncing plugin, refreshing cache, or checking for new…

romiluz13/cc10x · 108 tokens

03-release-tag

Cut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag.

ai-driven-dev/framework · 55 tokens

mcp-release-prep

Prepare an MCP server and plugin release by bumping versions across all files and updating changelog.

dathere/qsv · 24 tokens