release-prep

Synchronize versions across seven files and draft bilingual release notes.

286|24|Updated Dec 20, 2025
One-click install
npx skills add https://github.com/Fu-Jie/openwebui-extensions --skill release-prep-fu-jie
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-prep
Source: https://github.com/Fu-Jie/openwebui-extensions/tree/main/.gemini/skills/release-prep
Command: npx skills add https://github.com/Fu-Jie/openwebui-extensions --skill release-prep-fu-jie

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Replaces manual, scattered release chores with a single orchestrated workflow that ensures version alignment and release-notes consistency.

Core Features & Use Cases

  • Version sync across seven critical files including plugin code, documentation, and docs index pages.
  • Automatic bilingual release notes generation for English and Chinese.
  • Drafts a conventional-commits message and prepares a commit ready to stage (without pushing or PR creation).

Quick Start

Run the release-prep workflow to synchronize version numbers, generate bilingual release notes, and draft a conventional-commits message.

Frequently Asked Questions about release-prep

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

FAQPage Schema
How do I automate version sync across multiple files for a plugin release?

Bilingual release notes generation automatically creates English and Chinese documentation from your commit history, ensuring consistent release-note readiness across both languages without manual translation effort.

What's the best way to draft conventional-commits messages before staging a release?

Release preparation omits push and PR actions by design, validating all changes locally before staging to prevent premature remote commits and ensuring you retain full control over the final pull request submission.

Does this release-prep workflow handle push or PR creation automatically?

No, this release-prep workflow does not handle push or PR creation; it explicitly omits these actions, focusing solely on validating changes, synchronizing versions, and drafting a conventional-commits message ready for you to stage manually.

Why does manual release preparation cause version inconsistency in plugin repositories?

Manual release preparation causes version inconsistency because scattered chores across seven or more files inevitably lead to human error, making an orchestrated workflow necessary to enforce seven-location consistency and align plugin code with documentation.