Agent skill

Workclaw Release Prep

by haojing8312 in haojing8312/WorkClaw

A skill your agent uses when preparing a WorkClaw desktop release and you need AI to recommend the next version number, summarize changes since the last tag, and draft bilingual Chinese plus English…

Apache-2.0Auto-check passedDevelopment

Install Workclaw Release Prep

skills CLI
$ npx skills add haojing8312/WorkClaw --skill workclaw-release-prep -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install haojing8312/WorkClaw workclaw-release-prep --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/haojing8312/WorkClaw.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/workclaw-release-prep .claude/skills/workclaw-release-prep && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
workclaw-release-prep
GitHub stars
141
Token cost
~1k tokens
SKILL.md length
431 words
Files
1
Skills in repo
14
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when preparing a WorkClaw desktop release and you need AI to recommend the next version number, summarize changes since the last tag, and draft bilingual Chinese plus English…

  • Preparing a WorkClaw desktop release and you need AI to recommend the next version number
  • SKILL.md covers Overview, When to Use, Inspect First and Version Recommendation Rules, plus 3 more sections
  • Calls git
  • Summarize changes since the last tag

What it does

Workclaw Release Prep is an agent skill from haojing8312/WorkClaw. Use when preparing a WorkClaw desktop release and you need AI to recommend the next version number, summarize changes since the last tag, and draft bilingual Chinese plus English release notes for human confirmation before publishing.

Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Changelog and release notes and Translation. It works with Git and Tauri. The licence is Apache-2.0.

When your agent uses it

  • Preparing a WorkClaw desktop release and you need AI to recommend the next version number
  • Summarize changes since the last tag
  • Draft bilingual Chinese plus English release notes for human confirmation before publishing

Example prompts

  • “/workclaw-release-prep”

What it can do on your machine

Read from SKILL.md and the folder at commit 81ae074. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Workclaw Release Prep loads about 1k tokens when it runs. Until then it costs about 64 tokens; SKILL.md has 431 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~64
When it runs · the whole SKILL.md, loaded when a task matches
~1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from haojing8312/WorkClaw at commit 81ae074, republished under its Apache-2.0 licence (© haojing8312). 431 words, ~1,003 tokens.

Download SKILL.mdSave it as .claude/skills/workclaw-release-prep/SKILL.md (or your agent's skills folder).
name
workclaw-release-prep
description
Use when preparing a WorkClaw desktop release and you need AI to recommend the next version number, summarize changes since the last tag, and draft bilingual Chinese plus English release notes for human confirmation before publishing.

WorkClaw Release Prep

Overview

Use this skill before cutting a WorkClaw release. It recommends the next version, explains why, and drafts bilingual release notes. It does not publish anything.

When to Use

  • The user wants a release recommendation
  • The user wants AI to decide between patch, minor, or major
  • The user wants bilingual Chinese + English release notes
  • The user wants a confirmation-ready release package before tagging

Do not use this skill to push commits, create tags, or publish releases. Use workclaw-release-publish after confirmation.

Inspect First

  • git tag --sort=-creatordate
  • git log <last-tag>..HEAD --oneline
  • git log <last-tag>..HEAD --format=%H%n%s%n%b%n==END==
  • git diff --name-only <last-tag>..HEAD
  • For high-signal commits, inspect git show --stat --summary <sha>
  • apps/runtime/package.json
  • apps/runtime/src-tauri/Cargo.toml
  • apps/runtime/src-tauri/tauri.conf.json
  • .github/release-windows-notes.md
  • Any release-impacting docs or plans the user wants included

Before drafting release notes, build a short candidate user-visible changes list from:

  • commit titles and commit bodies
  • test names that describe user-facing behavior
  • provider or model names mentioned explicitly, such as Qwen, DeepSeek, OpenAI, Claude
  • compatibility, routing, transport, recovery, installer, branding, and skill/runtime keywords

Default rule: if a commit message or test name names a concrete model, provider, or desktop behavior, treat it as a release-note candidate unless there is strong evidence it is purely internal.

Version Recommendation Rules

  • Recommend patch for bug fixes, stability hardening, recovery improvements, small UX polish, or non-breaking desktop flow fixes
  • Recommend minor for clear new user-facing capabilities, new workflows, new navigation models, or meaningful product surface expansion
  • Recommend major only for breaking changes, migrations, compatibility breaks, or strong user behavior changes that require explicit upgrade communication

When uncertain, provide:

  • one recommended version
  • one conservative alternative
  • a short rationale for both
Show full SKILL.md (163 more words)Show less

Required Output

Use this shape:

md
## Release Prep
- Last tag:
- Recommended version:
- Alternative version:
- Why:
- Release scope:
- Files or areas reviewed:

## Candidate Highlights
- Included in notes:
- Intentionally omitted:
- Follow-up checks:

## Release Notes Draft
### 中文
- ...

### English
- ...

## Confirmation Needed
- Confirm version:
- Confirm release notes:
- Ready for publish skill: yes | no

Drafting Rules

  • Keep release notes concise and user-facing
  • Group changes by outcomes, not by files
  • Mention desktop installer guidance only if relevant
  • Avoid speculative claims not backed by repo changes
  • Chinese and English sections should say the same thing, not different things
  • Start from the candidate highlight list, then compress; do not draft directly from file paths alone
  • When a change improves compatibility for a named provider or model, prefer stating that user-facing outcome plainly
  • If a candidate highlight is omitted from the final notes, explain why in Intentionally omitted

Common Mistakes

  • Recommending minor for pure bugfix bundles without a new capability
  • Recommending patch when a clearly new workflow shipped
  • Mixing internal implementation detail into user-facing release notes
  • Reading only changed file paths and missing user-visible gains described in commit bodies or tests
  • Treating provider/model compatibility fixes as internal-only by default when they change whether users can actually run that provider
  • Proceeding to publish without explicit human confirmation

© haojing8312, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/workclaw-release-prep of haojing8312/WorkClaw.

Open the folder on GitHubat commit 81ae074

Compare with similar skills

Workclaw Release Prep next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Workclaw Release Prep compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Workclaw Release Prep this skillhaojing8312/WorkClaw141—~1kAutomated safety check: PassApache-2.0
Pulse Releasequnqin24/Pulse517—~1.3kAutomated safety check: PassApache-2.0
Releaseyicheng47/runner273—~1.8kAutomated safety check: PassMIT
QuickreleaseMooshieblob1/MooshieUI207—~1.1kAutomated safety check: PassAGPL-3.0
React Router Release Notes Prepremix-run/react-router57k—~1.1kAutomated safety check: PassMIT
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT

Similar skills

  • Pulse Release

    qunqin24/Pulse

    Release a new Pulse version end to end — checks, bilingual CHANGELOG entry, VERSION, tag, the release workflow, syncing main, and the issue replies that go with it.

    517 GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Release

    yicheng47/runner

    Cut a Runner production release — bump the workspace version, tag vX.Y.Z, let release.yml build the draft for both platforms, write bilingual release notes (English, with 中文 collapsed in a details…

    273 GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed
  • Quickrelease

    Mooshieblob1/MooshieUI

    Cuts a MooshieUI semver release quickly, skipping bot reviews, pre-commit-checks, and local build validation.

    207 GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed
  • React Router Release Notes Prep

    remix-run/react-router

    Polishes pending React Router change files before the versioning scripts run, and decides whether a long-form What's Changed section is warranted.

    57k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed
  • Draft Release Notes

    jamiepine/voicebox

    Writes or refreshes the Unreleased section of CHANGELOG.md as a themed narrative built from the commits, PRs and diff since the last version tag.

    57k GitHub stars~941 tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Publishes curated, bilingual release notes for an existing Mole version tag with gh release edit, including contributor thanks and reactions, after the release workflow finishes.

    70k GitHub stars~1.9k tokensUpdated today
    DevelopmentAuto-check passed

More from haojing8312/WorkClaw

All 14 skills in this repo
  • Design Style Skill

    haojing8312/WorkClaw

    Select a consistent visual design system for PPT slides using radius/spacing style recipes.

    141 GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed
  • Slack Messaging

    haojing8312/WorkClaw

    A skill your agent uses when asked to send or read Slack messages, check Slack channels, test Slack integrations, or interact with a Slack workspace from the command line.

    141 GitHub stars~897 tokensUpdated 4 mo ago
    Auto-check passed
  • Ppt Editing Skill

    haojing8312/WorkClaw

    Edit existing PowerPoint files or templates with XML-safe workflows.

    141 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • Slide Making Skill

    haojing8312/WorkClaw

    Implement single-slide PowerPoint pages with PptxGenJS. An agent skill from haojing8312/WorkClaw.

    141 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed
  • Workclaw Change Verification

    haojing8312/WorkClaw

    A skill your agent uses when changes affect runtime code, tests, skill assets, or build and test behavior in WorkClaw and verification is required before claiming completion.

    141 GitHub stars~555 tokensUpdated 4 mo ago
    Auto-check passed
  • A skill your agent uses when changing runtime behavior, routing, provider integration, tool permissions, sidecar protocols, or vendor sync boundaries in WorkClaw before editing code.

    141 GitHub stars~575 tokensUpdated 4 mo ago
    Auto-check passed

Works with

Categories

Questions about Workclaw Release Prep

What does Workclaw Release Prep do?

A skill your agent uses when preparing a WorkClaw desktop release and you need AI to recommend the next version number, summarize changes since the last tag, and draft bilingual Chinese plus English…. Workclaw Release Prep is an agent skill from haojing8312/WorkClaw. Use when preparing a WorkClaw desktop release and you need AI to recommend the next version number, summarize changes since the last tag, and draft bilingual Chinese plus English release notes for human confirmation before publishing.

When should I use Workclaw Release Prep?

Workclaw Release Prep fits situations like: preparing a WorkClaw desktop release and you need AI to recommend the next version number; summarize changes since the last tag; draft bilingual Chinese plus English release notes for human confirmation before publishing.

How do I install Workclaw Release Prep in Claude Code?

Run `npx skills add haojing8312/WorkClaw --skill workclaw-release-prep -a claude-code`. Or copy the skill folder (.agents/skills/workclaw-release-prep in haojing8312/WorkClaw) into .claude/skills/workclaw-release-prep in your project. Claude Code loads it when a task matches its description.

How do I install Workclaw Release Prep in Codex?

Run `npx skills add haojing8312/WorkClaw --skill workclaw-release-prep -a codex`. Or copy the skill folder (.agents/skills/workclaw-release-prep in haojing8312/WorkClaw) into .agents/skills/workclaw-release-prep in your project. Codex loads it when a task matches its description.

Can I use Workclaw Release Prep in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add haojing8312/WorkClaw --skill workclaw-release-prep -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/workclaw-release-prep, .gemini/skills/workclaw-release-prep, .github/skills/workclaw-release-prep and .opencode/skills/workclaw-release-prep in your project.

What does Workclaw Release Prep need to run?

Going by SKILL.md and its folder, Workclaw Release Prep needs the command-line tools its instructions call (git).

Does Workclaw Release Prep access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Workclaw Release Prep safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Workclaw Release Prep use?

Workclaw Release Prep is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Workclaw Release Prep use?

About 1k tokens (SKILL.md is roughly 4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Workclaw Release Prep?

Skills that share tags, products or a category with Workclaw Release Prep: Pulse Release (qunqin24/Pulse, 517 stars), Release (yicheng47/runner, 273 stars), Quickrelease (Mooshieblob1/MooshieUI, 207 stars) and React Router Release Notes Prep (remix-run/react-router, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Workclaw Release Prep?

haojing8312 (a GitHub user) maintains it in haojing8312/WorkClaw, which has 141 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on May 27, 2026.

Source: haojing8312/WorkClaw on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.