Worktrunk Release Workflow
max-sixty/worktrunk
Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.
Prepare parse-display release changes before publishing with a Rust Cargo script when nightly Cargo is available.
Install Prepare Release
$ npx skills add frozenlib/parse-display --skill prepare-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install frozenlib/parse-display prepare-release --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/frozenlib/parse-display.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.codex/skills/prepare-release .claude/skills/prepare-release && rm -rf skills-srcUse ~/.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/
Install the "prepare-release" agent skill from https://github.com/frozenlib/parse-display/tree/master/.codex/skills/prepare-release into .claude/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-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 install https://github.com/frozenlib/parse-display/tree/master/.codex/skills/prepare-releaseType 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.
$ npx skills add frozenlib/parse-display --skill prepare-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install frozenlib/parse-display prepare-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/frozenlib/parse-display.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.codex/skills/prepare-release .agents/skills/prepare-release && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "prepare-release" agent skill from https://github.com/frozenlib/parse-display/tree/master/.codex/skills/prepare-release into .agents/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-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.
$ npx skills add frozenlib/parse-display --skill prepare-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install frozenlib/parse-display prepare-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/frozenlib/parse-display.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.codex/skills/prepare-release .cursor/skills/prepare-release && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "prepare-release" agent skill from https://github.com/frozenlib/parse-display/tree/master/.codex/skills/prepare-release into .cursor/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-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 https://github.com/frozenlib/parse-display.git --path .codex/skills/prepare-release--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add frozenlib/parse-display --skill prepare-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install frozenlib/parse-display prepare-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/frozenlib/parse-display.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.codex/skills/prepare-release .gemini/skills/prepare-release && rm -rf skills-srcUse ~/.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/
Install the "prepare-release" agent skill from https://github.com/frozenlib/parse-display/tree/master/.codex/skills/prepare-release into .gemini/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-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.
$ gh skill install frozenlib/parse-display prepare-releaseInstalls 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).
$ npx skills add frozenlib/parse-display --skill prepare-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/frozenlib/parse-display.git skills-src && mkdir -p .github/skills && cp -r skills-src/.codex/skills/prepare-release .github/skills/prepare-release && rm -rf skills-srcUse ~/.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/
Install the "prepare-release" agent skill from https://github.com/frozenlib/parse-display/tree/master/.codex/skills/prepare-release into .github/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-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.
$ npx skills add frozenlib/parse-display --skill prepare-release -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install frozenlib/parse-display prepare-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/frozenlib/parse-display.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.codex/skills/prepare-release .opencode/skills/prepare-release && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "prepare-release" agent skill from https://github.com/frozenlib/parse-display/tree/master/.codex/skills/prepare-release into .opencode/skills/prepare-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "prepare-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
prepare-release- GitHub stars
- 193
- Token cost
- ~1.3k tokens
- SKILL.md length
- 507 words
- Files
- 3 (incl. scripts)
- Skills in repo
- 1
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Prepare parse-display release changes before publishing with a Rust Cargo script when nightly Cargo is available.
- Works in 3 steps: Extract the target version from the… → Confirm the repository root is the… → Prefer the bundled Cargo script when…
- Codex is asked to prepare a parse-display release
- SKILL.md covers Workflow and Notes
- Runs Rust scripts from its folder; calls git, cargo and rg
What it does
Prepare Release is an agent skill from frozenlib/parse-display. Prepare parse-display release changes before publishing with a Rust Cargo script when nightly Cargo is available. Use when Codex is asked to prepare a parse-display release, bump parse-display to a requested version, move CHANGELOG.md Unreleased entries into a release section, update parse-display-derive only when it changed since the previous version commit, commit the release prep, and create the release git tag.
Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including scripts (for example `agents/openai.yaml`).
It sits in Development, covering Changelog and release notes. It works with Rust and Git. The repository describes itself as: Procedural macro to implement Display and FromStr using common settings. The licence is Apache-2.0.
When your agent uses it
- Codex is asked to prepare a parse-display release
- Bump parse-display to a requested version
- Move CHANGELOG.md Unreleased entries into a release section
- Update parse-display-derive only when it changed since the previous version commit
Example prompts
- “/prepare-release”
Requirements
- Python 3
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Extract the target version from the user's request.
- Confirm the repository root is the parse-display workspace.
- Prefer the bundled Cargo script when nightly Cargo supports -Zscript.
What it can do on your machine
Read from SKILL.md and the folder at commit 45e8b51. 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
Ships 1 file in scripts/ (Rust), which the agent can run.
Shell commands in SKILL.md call:
gitcargorg
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
Prepare Release loads about 1.3k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 507 words of instructions outside code blocks.
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); the scripts in this folder are not scanned.
SKILL.md
The full file from frozenlib/parse-display at commit 45e8b51, republished under its Apache-2.0 licence (© frozenlib). 507 words, ~1,319 tokens.
Download SKILL.mdSave it as
.claude/skills/prepare-release/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- prepare-release
- description
- Prepare parse-display release changes before publishing with a Rust Cargo script when nightly Cargo is available. Use when Codex is asked to prepare a parse-display release, bump parse-display to a requested version, move CHANGELOG.md Unreleased entries into a release section, update parse-display-derive only when it changed since the previous version commit, commit the release prep, and create the release git tag.
Prepare Release
Workflow
- Extract the target version from the user's request.
- Accept only an explicit version such as
0.11.0. - If the user did not provide a version, do not modify files. Show next-version candidates, ask the user to provide the target version, and end the turn.
- Prefer using the bundled Cargo script with no version to show candidates:
- Accept only an explicit version such as
cargo +nightly -Zscript .codex\skills\prepare-release\scripts\prepare_release.rsConfirm the repository root is the parse-display workspace.
- Work from the directory containing
Cargo.toml,CHANGELOG.md,parse-display/Cargo.toml, andparse-display-derive/Cargo.toml. - Inspect
git status --shortbefore editing. Do not include unrelated user changes in the release commit. - Do not use Python scripts for this workflow.
- Work from the directory containing
Prefer the bundled Cargo script when nightly Cargo supports
-Zscript.
cargo +nightly -Zscript .codex\skills\prepare-release\scripts\prepare_release.rs --dry-run <version>
cargo +nightly -Zscript .codex\skills\prepare-release\scripts\prepare_release.rs <version>The script updates release files only. It never commits and never creates tags.
In sandboxed Codex environments, cargo +nightly -Zscript may need approval because Cargo writes build artifacts under Cargo's cache directory.
- If
cargo +nightly -Zscriptis unavailable, make the same edits manually.- Set
parse-display/Cargo.tomlpackageversionto<version>. - Update
Cargo.lock'sparse-displaypackage version to<version>. - Search docs and Rust doc comments for the previous parse-display version and update only active parse-display version references, such as dependency snippets and current-version docs links.
- Do not update docs.rs links for deprecated features. Deprecated feature documentation must keep linking to the older version where that deprecated feature is still documented.
- Set
rg -n '<old-version>|parse-display = "' README.md parse-display parse-display-with- Decide whether to update
parse-display-derive.- Find the previous version commit:
git log --format=%H --extended-regexp --grep "^Version [0-9]+\.[0-9]+\.[0-9]+\.$" -n 1- Check whether
parse-display-derivechanged since that commit:
git diff --name-only <previous-version-commit>..HEAD -- parse-display-derive
git status --porcelain -- parse-display-derive- If either command shows changes, set
parse-display-derive/Cargo.tomlpackageversionto<version>, setparse-display/Cargo.toml'sparse-display-derivedependency version to=<version>, and updateCargo.lock'sparse-display-derivepackage version to<version>. - If there are no changes, leave
parse-display-derive/Cargo.toml, the dependency version, and the lockfile'sparse-display-deriveversion unchanged.
Update
CHANGELOG.mdmanually only if the Cargo script was not used.- Insert
## [<version>] - YYYY-MM-DDimmediately after theUnreleasedblock, using the current local date. - Move every non-empty category body from
Unreleasedinto the same category under the new version. - Add only categories with at least one item under the new version.
- Leave
Unreleasedwith category headings only. Preserve these headings unless the file already uses a different category set:Added,Changed,Deprecated,Removed,Fixed,Performance,Security. - Update the compare links at the bottom:
- Change
[unreleased]to comparev<version>...HEAD. - Add
[<version>]: https://github.com/frozenlib/parse-display/compare/v<previous-version>...v<version>immediately after[unreleased].
- Change
- Insert
Verify the result.
- Inspect
git diff -- CHANGELOG.md parse-display/Cargo.toml parse-display-derive/Cargo.toml Cargo.lock README.md parse-display/src parse-display-with/src. - Confirm
CHANGELOG.mdhas a non-empty section for the new version and only empty category headings underUnreleased. - Run the repository's normal Rust validation when practical, at minimum
cargo check --workspace.
- Inspect
Commit only the release-prep files.
- Stage the files changed by the release workflow.
- Commit with exactly
Version <version>. - Do not add unrelated worktree changes to this commit.
Show full SKILL.md (59 more words)Show less
git commit -m "Version <version>."- Create the release tag after the commit succeeds.
git tag "v<version>"Notes
- Do not create the tag before the release commit exists.
- If the tag already exists, stop and report the conflict.
- If changelog
Unreleasedhas no items, still create the version section only if the user explicitly wants that release; otherwise report that there are no changelog entries to release.
© frozenlib, 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
SKILL.md and 2 other files (scripts) in .codex/skills/prepare-release of frozenlib/parse-display.
- SKILL.md
- agents/openai.yaml
- scripts/prepare_release.rs
Open the folder on GitHubat commit 45e8b51
Compare with similar skills
Prepare Release 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Prepare Release this skillfrozenlib/parse-display | 193 | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| Worktrunk Release Workflowmax-sixty/worktrunk | 8.9k | — | ~6.9k | Automated safety check: Pass | Custom licence | |
| Releasexin2017338/lynx-proxy | 502 | — | ~1.1k | Automated safety check: Pass | MIT | |
| Releaseyicheng47/runner | 269 | — | ~1.8k | Automated safety check: Pass | MIT | |
| Release Crater3bl-org/r3bl-open-core | 485 | — | ~2.4k | Automated safety check: Pass | Apache-2.0 | |
| Release Managementtermide/termide | 171 | — | ~6.8k | Automated safety check: Pass | MIT |
Similar skills
Release
xin2017338/lynx-proxy
Publish a new release version of Lynx Proxy. An agent skill from xin2017338/lynx-proxy.
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…
Release Crate
r3bl-org/r3bl-open-core
Publish a crate release to crates.io with changelog, standalone release notes, git tag, and GitHub release.
Release Management
termide/termide
Prepare and publish a project release with version updates, changelog generation, tagging, and validation
Quickrelease
Mooshieblob1/MooshieUI
Cuts a MooshieUI semver release quickly, skipping bot reviews, pre-commit-checks, and local build validation.
Related
Categories
Questions about Prepare Release
What does Prepare Release do?
Prepare parse-display release changes before publishing with a Rust Cargo script when nightly Cargo is available. Prepare Release is an agent skill from frozenlib/parse-display. Prepare parse-display release changes before publishing with a Rust Cargo script when nightly Cargo is available.
When should I use Prepare Release?
Prepare Release fits situations like: Codex is asked to prepare a parse-display release; bump parse-display to a requested version; move CHANGELOG.md Unreleased entries into a release section; update parse-display-derive only when it changed since the previous version commit.
How do I install Prepare Release in Claude Code?
Run `npx skills add frozenlib/parse-display --skill prepare-release -a claude-code`. Or copy the skill folder (.codex/skills/prepare-release in frozenlib/parse-display) into .claude/skills/prepare-release in your project. Claude Code loads it when a task matches its description.
How do I install Prepare Release in Codex?
Run `npx skills add frozenlib/parse-display --skill prepare-release -a codex`. Or copy the skill folder (.codex/skills/prepare-release in frozenlib/parse-display) into .agents/skills/prepare-release in your project. Codex loads it when a task matches its description.
Can I use Prepare Release 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 frozenlib/parse-display --skill prepare-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/prepare-release, .gemini/skills/prepare-release, .github/skills/prepare-release and .opencode/skills/prepare-release in your project.
What does Prepare Release need to run?
Going by SKILL.md and its folder, Prepare Release needs Rust for the scripts in its folder and the command-line tools its instructions call (git, cargo and rg). Our summary lists: Python 3.
Does Prepare Release 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 Prepare Release 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Prepare Release use?
Prepare Release 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 Prepare Release use?
About 1.3k tokens (SKILL.md is roughly 5.3k 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 Prepare Release?
Skills that share tags, products or a category with Prepare Release: Worktrunk Release Workflow (max-sixty/worktrunk, 8.9k stars), Release (xin2017338/lynx-proxy, 502 stars), Release (yicheng47/runner, 269 stars) and Release Crate (r3bl-org/r3bl-open-core, 485 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Prepare Release?
frozenlib (a GitHub user) maintains it in frozenlib/parse-display, which has 193 GitHub stars. The repository was last updated on October 4, 2026.
Source: frozenlib/parse-display on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.