qwenvoice-release-publish

Name: qwenvoice-release-publish
Availability: InStock
Author: powerbeef

Coordinate QwenVoice release publishing with dual-UI GitHub Actions workflows.

350|30|Updated Feb 21, 2026

Search Tags:#versioning #github-actions #release-notes #artifact-verification #ci-gates #release-publishing #dual-ui

Ready to run

npx skills add https://github.com/PowerBeef/QwenVoice --skill qwenvoice-release-publish

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qwenvoice-release-publish
Source: https://github.com/PowerBeef/QwenVoice/tree/main/.agents/skills/qwenvoice-release-publish
Command: npx skills add https://github.com/PowerBeef/QwenVoice --skill qwenvoice-release-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Publishing QwenVoice releases requires coordinating versioning metadata, release notes, and artifacts with the target tag to enable reliable public releases.

Core Features & Use Cases

Dual-UI release workflow orchestration for macOS packaging and GitHub Releases.
Release notes governance requiring checked-in docs at docs/releases/vX.Y.md.
Preflight validation to ensure metadata, SHAs, and assets align before publishing.

Quick Start

Follow the guided steps to prepare and publish a new release.

Frequently Asked Questions about qwenvoice-release-publish

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

FAQPage Schema

How do I automate release publishing for macOS builds using GitHub Actions?▼

Automate release publishing by orchestrating a dual-UI GitHub Actions workflow that aligns metadata, notes, and artifacts with the target tag across macOS 15 and 26 builds. This coordinates versioned release publishing to produce a correct, signed, and hosted release.

What are release notes governance requirements for versioned GitHub Releases?▼

Release notes governance requires checked-in documentation at docs/releases/vX.Y.md before publishing. This ensures release notes are properly tracked and aligned with the target tag to enable reliable public releases.

How does preflight validation ensure committed SHAs match published artifacts?▼

Preflight validation verifies committed SHAs match published artifacts by applying CI gates that check metadata, SHAs, and assets align before publishing. This prevents mismatched releases and ensures artifact integrity.

Can I use this dual-UI workflow for both macOS 15 and macOS 26 builds?▼

Yes, the dual-UI GitHub Actions workflow applies across both macOS 15 and 26 builds. It coordinates versioned release publishing by aligning metadata, notes, and artifacts with the target tag for each platform.

What input requirements must be satisfied before publishing a signed release?▼

You must satisfy preflight gates, input requirements, and the release notes path before publishing. This includes aligning metadata, notes, and artifacts with the target tag to produce a correct, signed, and hosted release.

Why does versioned release publishing require coordinating metadata with the target tag?▼

Versioned release publishing requires coordination because metadata, release notes, and artifacts must align with the target tag to enable reliable public releases. Misalignment causes mismatched SHAs, missing notes, or unsigned artifacts.