skills.rest
haojing8312
haojing8312COMMUNITY
Explore all skills by this author →
GitHub

workclaw-release-publish

Publish a confirmed WorkClaw release with git tag and Windows installer.

154|1|Updated Feb 20, 2026
Search Tags:#git#versioning#packaging#release#ci#release-notes#windows-installer
One-click install
npx skills add https://github.com/haojing8312/WorkClaw --skill workclaw-release-publish
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: workclaw-release-publish
Source: https://github.com/haojing8312/WorkClaw/tree/main/.agents/skills/workclaw-release-publish
Command: npx skills add https://github.com/haojing8312/WorkClaw --skill workclaw-release-publish

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill codifies the final human-approved release publication workflow for WorkClaw to ensure version consistency, run required release checks, push the canonical tag, and produce a local Windows installer without manual mistakes.

Core Features & Use Cases

  • Release metadata synchronization: update apps/runtime/package.json, Cargo.toml, and tauri.conf.json so all runtime version files match the approved tag.
  • Verification and packaging: run release checks and test suites, build the runtime, and produce local .exe or .msi artifacts while triggering remote CI via a pushed tag.
  • Use Case: After a manager confirms version vX.Y.Z and bilingual release notes, execute this workflow to commit release changes, push main, create and push the tag, and provide local installer paths for QA and distribution.

Quick Start

Publish version v2.3.0 with the confirmed bilingual release notes, run the release checks and packaging, push main, create and push the tag, and report the local Windows installer path.

Frequently Asked Questions about workclaw-release-publish

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

FAQPage Schema
How do I automate git tagging and Windows installer packaging for desktop release publishing?▼

Desktop release publishing automates git tagging and Windows installer packaging by running release checks, committing version updates, pushing tags to trigger CI workflows, and generating local .exe or .msi artifacts.

What steps are required to synchronize runtime version files before creating a git release tag?▼

Synchronizing runtime version files requires updating apps/runtime/package.json, Cargo.toml, and tauri.conf.json to match the approved tag, ensuring version consistency before committing changes and pushing the git release tag.

Does release publishing require human-reviewed bilingual release notes before triggering CI packaging?▼

Yes, release publishing requires human-reviewed bilingual Chinese and English release notes alongside a confirmed version number before running release checks, pushing main, and triggering CI packaging workflows.

What verification checks must pass before pushing a git tag for desktop application distribution?▼

Verification checks before pushing a git tag include version consistency checks, release tests, installer tests, docs tests, e2e tests, and build packaging to ensure desktop application distribution integrity.

Can I produce a local Windows installer without manually updating tauri.conf.json and Cargo.toml?▼

Yes, the release workflow automatically updates tauri.conf.json and Cargo.toml to match the approved version, builds the runtime, and produces local Windows installer artifacts without manual file editing.

Why does desktop release publishing fail if version numbers differ across package.json and Cargo.toml?▼

Desktop release publishing fails because version consistency checks enforce that package.json, Cargo.toml, and tauri.conf.json must match the approved tag before committing changes and creating the git tag.

Related Skills

Explore More Software Engineering Skills→
bradhannahbradhannah
2

homebrew-release

Automate Homebrew releases with version sync across Tauri and Cargo files.

Community
Advanced
grtninjagrtninja
2

repo-d-local-packaging

Automate Windows packaging validation and capture command and artifact evidence.

Community
Intermediate
PavelLizunovPavelLizunov
3

ship-rolling-candidate

Automate versioning, build orchestration, and GitHub release management for rolling release candidates.

Community
Advanced
mikha08-rgbmikha08-rgb
12

release-guardian

Synchronize version numbers across VoiceLite project files and release workflow.

Community
Intermediate