Agent skill

Worktrunk Release Workflow

Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.

Custom licenceAuto-check passedDevelopment

Install Worktrunk Release Workflow

skills CLI

$ npx skills add max-sixty/worktrunk --skill release -a claude-code

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

GitHub CLI

$ gh skill install max-sixty/worktrunk release --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/max-sixty/worktrunk.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/release .claude/skills/release && 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/

Paste into Claude Code

Install the "release" agent skill from https://github.com/max-sixty/worktrunk/tree/main/.claude/skills/release into .claude/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/max-sixty/worktrunk/tree/main/.claude/skills/release

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add max-sixty/worktrunk --skill release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install max-sixty/worktrunk release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/max-sixty/worktrunk.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/release .agents/skills/release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "release" agent skill from https://github.com/max-sixty/worktrunk/tree/main/.claude/skills/release into .agents/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add max-sixty/worktrunk --skill release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install max-sixty/worktrunk release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/max-sixty/worktrunk.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/release .cursor/skills/release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "release" agent skill from https://github.com/max-sixty/worktrunk/tree/main/.claude/skills/release into .cursor/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/max-sixty/worktrunk.git --path .claude/skills/release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add max-sixty/worktrunk --skill release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install max-sixty/worktrunk release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/max-sixty/worktrunk.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/release .gemini/skills/release && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "release" agent skill from https://github.com/max-sixty/worktrunk/tree/main/.claude/skills/release into .gemini/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install max-sixty/worktrunk release

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add max-sixty/worktrunk --skill release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/max-sixty/worktrunk.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/release .github/skills/release && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "release" agent skill from https://github.com/max-sixty/worktrunk/tree/main/.claude/skills/release into .github/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add max-sixty/worktrunk --skill release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install max-sixty/worktrunk release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/max-sixty/worktrunk.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/release .opencode/skills/release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "release" agent skill from https://github.com/max-sixty/worktrunk/tree/main/.claude/skills/release into .opencode/skills/release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "release", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: release
GitHub stars: 8.9k
Token cost: ~6.9k tokens
SKILL.md length: 3,351 words
Files: 3
Skills in repo: 3
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: Custom licence

At a glance

Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.

Works in 12 steps: Sync the release branch with main: The… → Run tests: Two gates — the local suite… → Check current version: Read version in… → …
Asked to do a release or cut a new Worktrunk version
SKILL.md covers Steps, Data-Loss Surface Review, CHANGELOG Review and Determine Release Type, plus 2 more sections
Calls git, cargo and gh; reaches github.com and worktrunk.dev

What it does

This is the release procedure for the Worktrunk project, a Git worktree CLI. It starts by bringing the release branch level with main using a fast-forward-only merge, so a stale branch cannot quietly leave out recent work, and it stops for manual reconciliation if the branches have diverged. The commit it lands on is noted as the tip the changelog has to cover.

Before releasing it requires two test gates: a local pre-merge hook run through cargo, and a nightly GitHub workflow dispatched on the same commit, which carries the full Linux, macOS and Windows suite. The agent watches that run to the end and fixes failures first. It then reads the current version from Cargo.toml, reviews the commits since the last release, and audits the combined diff for anything that could lose user data.

The excerpt is cut off before the later steps, but the description says the workflow ends with publishing the new version to crates.io and GitHub. An evals folder in the skill holds a README and a research note.

When your agent uses it

Asked to do a release or cut a new Worktrunk version
Publishing a new version to crates.io and GitHub
Checking that the release branch is not behind main before tagging
Auditing the changes since the last release for data-loss risks

Example prompts

“Do a release of worktrunk.”
“Cut a new release and publish it to crates.io and GitHub once the nightly run is green.”
“Before we release, check what has merged since the last version and flag anything that could delete user data.”

Requirements

Git and the GitHub CLI (`gh`)
A Rust toolchain with cargo
Maintainer rights to publish to crates.io and GitHub

Workflow steps

12 steps, taken from the first numbered list in SKILL.md.

Sync the release branch with main: The release worktree's branch lags main between releases — it's only reset to main after a release…
Run tests: Two gates — the local suite and the full cross-platform suite.
Check current version: Read version in Cargo.toml
Review commits: Check commits since last release to understand scope of changes. Audit the cumulative diff for the data-loss surface (see…
Check library API compatibility (advisory): Run cargo semver-checks check-release -p worktrunk (install with cargo install…
Credit contributors: Check for external PR authors and issue reporters (see "Credit External Contributors" and "Credit Issue Reporters"…
Determine release type: Pick the bump from the changes (including semver-checks result). Ask the user only if the choice is genuinely…
Bump version (must run on a clean tree — before editing CHANGELOG)
Update CHANGELOG: the top section holds this release's changes (see MANDATORY verification below). If it is ## Unreleased, rename that…
Commit: Reset the auto-commit from step 8, stage everything, and create the final release commit
Merge to main: push the release branch, open a PR, wait for CI, and merge it. Keep the worktree — the remaining steps run from it. Then…
Verify the changelog covers main, then tag and push: the tag decides what ships — release.yaml builds the binaries and the GitHub release…

What it can do on your machine

Read from SKILL.md and the folder at commit dea4029. 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
- cargo
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- github.com
- worktrunk.dev
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

Worktrunk Release Workflow loads about 6.9k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 3,351 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 3,351 words (~6,874 tokens).

“--ff-only advances the branch when it's a strict ancestor of origin/main and fails (rather than creating a merge commit or discarding work) if it has diverged — reconcile manually before continuing. This is the release-branch equivalent of wt up, spelled…”

— opening of SKILL.md by max-sixty, Custom licence

name: release
metadata.internal: true

Read the full SKILL.md on GitHub

Files

SKILL.md and 2 other files in .claude/skills/release of max-sixty/worktrunk.

SKILL.md
evals/README.md
evals/research-0.80.0.md

Open the folder on GitHubat commit dea4029

Compare with similar skills

Worktrunk Release Workflow 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.

Worktrunk Release Workflow compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Worktrunk Release Workflow this skillmax-sixty/worktrunk	8.9k	—	~6.9k	Automated safety check: Pass	Custom licence	today
Codex Proxy RS Releasezyycn/codex-proxy-rs	738	—	~327	Automated safety check: Pass	Apache-2.0	today
Release312362115/claude	107	—	~874	Automated safety check: Pass	MIT	4 mo ago
Hunk Release Workflowmodem-dev/hunk	9.5k	—	~3.8k	Automated safety check: Pass	MIT	today
Coffee GB Releasetrekawek/coffee-gb	1.2k	—	~1.4k	Automated safety check: Pass	MIT	6 days ago
ZCF Release AutomationUfoMiao/zcf	6.1k	—	~3.4k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Codex Proxy RS Release
zyycn/codex-proxy-rs
Plans versions, writes release notes, publishes stable or pre-release builds and recovers from failed releases for Codex Proxy RS, without covering deploys or tag cleanup.
738 GitHub stars~327 tokensUpdated today
DevelopmentAuto-check passed
Release
312362115/claude
发版自动化技能：CalVer 版本号 + 从 git log 生成 changelog + GitHub Releases。
107 GitHub stars~874 tokensUpdated 4 mo ago
DevelopmentAuto-check passed
Hunk Release Workflow
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
9.5k GitHub stars~3.8k tokensUpdated today
DevelopmentAuto-check passed
Coffee GB Release
trekawek/coffee-gb
Releases the current Coffee GB Maven snapshot through the GitHub Maven release workflow, then verifies and curates the tag and GitHub release.
1.2k GitHub stars~1.4k tokensUpdated 6 days ago
DevelopmentAuto-check passed
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
6.1k GitHub stars~3.4k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
ClawRouter Release Checklist
BlockRunAI/ClawRouter
Walks the agent through every ClawRouter release step in order, from the version bump and changelog entry to build, tests, npm publish, git tag and GitHub release.
6.6k GitHub stars~1.4k tokensUpdated 2 days ago
DevelopmentAuto-check passed

Questions about Worktrunk Release Workflow

What does Worktrunk Release Workflow do?

Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish. This is the release procedure for the Worktrunk project, a Git worktree CLI. It starts by bringing the release branch level with main using a fast-forward-only merge, so a stale branch cannot quietly leave out recent work, and it stops for manual reconciliation if the branches have diverged.

When should I use Worktrunk Release Workflow?

Worktrunk Release Workflow fits situations like: asked to do a release or cut a new Worktrunk version; publishing a new version to crates.io and GitHub; checking that the release branch is not behind main before tagging; auditing the changes since the last release for data-loss risks.

How do I install Worktrunk Release Workflow in Claude Code?

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

How do I install Worktrunk Release Workflow in Codex?

Run `npx skills add max-sixty/worktrunk --skill release -a codex`. Or copy the skill folder (.claude/skills/release in max-sixty/worktrunk) into .agents/skills/release in your project. Codex loads it when a task matches its description.

Can I use Worktrunk Release Workflow 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 max-sixty/worktrunk --skill release -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/release, .gemini/skills/release, .github/skills/release and .opencode/skills/release in your project.

What does Worktrunk Release Workflow need to run?

Going by SKILL.md and its folder, Worktrunk Release Workflow needs the command-line tools its instructions call (git, cargo and gh). Our summary lists: Git and the GitHub CLI (`gh`); A Rust toolchain with cargo; Maintainer rights to publish to crates.io and GitHub.

Does Worktrunk Release Workflow access the network?

SKILL.md names 2 domains. In commands or code: github.com and worktrunk.dev; the agent is likely to contact these when it follows the instructions. This is read from the text; nothing was executed.

Is Worktrunk Release Workflow 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 Worktrunk Release Workflow use?

Worktrunk Release Workflow has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Worktrunk Release Workflow use?

About 6.9k tokens (SKILL.md is roughly 27k 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 Worktrunk Release Workflow?

Skills that share tags, products or a category with Worktrunk Release Workflow: Codex Proxy RS Release (zyycn/codex-proxy-rs, 738 stars), Release (312362115/claude, 107 stars), Hunk Release Workflow (modem-dev/hunk, 9.5k stars) and Coffee GB Release (trekawek/coffee-gb, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Worktrunk Release Workflow?

max-sixty (a GitHub user) maintains it in max-sixty/worktrunk, which has 8,920 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

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

Worktrunk Release Workflow

Install Worktrunk Release Workflow

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

Codex Proxy RS Release

Release

Hunk Release Workflow

Coffee GB Release

ZCF Release Automation

ClawRouter Release Checklist

More from max-sixty/worktrunk

Worktrunk Tend CI Guidance

Worktrunk CLI Output Rules

Questions about Worktrunk Release Workflow

Install Worktrunk Release Workflow

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

More from max-sixty/worktrunk

Related

Questions about Worktrunk Release Workflow