New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Lade Release

by zifeo in zifeo/lade

Prepare a Lade release: update CHANGELOG.md and bump crate versions with cargo set-version.

MPL-2.0Auto-check passedDevelopment

Install Lade Release

skills CLI
$ npx skills add zifeo/lade --skill lade-release -a claude-code

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

GitHub CLI
$ gh skill install zifeo/lade lade-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/zifeo/lade.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.cursor/skills/lade-release .claude/skills/lade-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/

Facts

Skill name
lade-release
GitHub stars
133
Token cost
~749 tokens
SKILL.md length
275 words
Files
1
Skills in repo
2
Repo updated
First seen
Licence
MPL-2.0

At a glance

Prepare a Lade release: update CHANGELOG.md and bump crate versions with cargo set-version.

  • Works in 5 steps: Find the base tag → Read [Unreleased] in CHANGELOG.md. Every… → Cross-check commits since the last tag.… → …
  • Cutting a release
  • SKILL.md covers Scope, Changelog workflow, Version bump and GitHub release notes, plus 1 more section
  • Calls cargo, git and bash; reaches github.com

What it does

Lade Release is an agent skill from zifeo/lade. Prepare a Lade release: update CHANGELOG.md and bump crate versions with cargo set-version. Use when cutting a release, tagging vX.Y.Z, publishing to GitHub Releases, or finalizing the changelog before a version bump.

Its SKILL.md is about 750 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 Secrets management. It works with GitHub, Bash, Rust and Kubernetes. The repository describes itself as: Temporary access to secrets and private networks for one command, then gone. Same wrap for humans and agents. See which access was used. The licence is MPL-2.0.

When your agent uses it

  • Cutting a release
  • Publishing to GitHub Releases
  • Finalizing the changelog before a version bump

Example prompts

  • “/lade-release”

Workflow steps

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

  1. Find the base tag
  2. Read [Unreleased] in CHANGELOG.md. Every user-facing item there should land in the new version section.
  3. Cross-check commits since the last tag. Add anything missing from [Unreleased] (group under Added / Changed / Fixed / Removed). Skip…
  4. Promote [Unreleased] → [X.Y.Z] - YYYY-MM-DD
  5. Writing style (match existing entries)

What it can do on your machine

Read from SKILL.md and the folder at commit 429000b. 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:

    • cargo
    • git
    • bash

    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

    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

Lade Release loads about 749 tokens when it runs. Until then it costs about 58 tokens; SKILL.md has 275 words of instructions outside code blocks.

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

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 zifeo/lade at commit 429000b, republished under its MPL-2.0 licence (© zifeo). 275 words, ~749 tokens.

Download SKILL.mdSave it as .claude/skills/lade-release/SKILL.md (or your agent's skills folder).
name
lade-release
description
Prepare a Lade release: update CHANGELOG.md and bump crate versions with cargo set-version. Use when cutting a release, tagging vX.Y.Z, publishing to GitHub Releases, or finalizing the changelog before a version bump.

Lade release

Scope

Release prep touches:

  • CHANGELOG.md (Keep a Changelog format)
  • Crate versions via cargo set-version --workspace (lade, lade-sdk, age-plugin-lade, including path deps)
  • Crate versions only. There is no APM package.

Never commit, tag, or push — the user handles git.

Changelog workflow

  1. Find the base tag

    bash
    git tag --sort=-v:refname | head -5
git log <last-tag>..HEAD --format="%h %s"

  2. Read [Unreleased] in CHANGELOG.md. Every user-facing item there should land in the new version section.

  3. Cross-check commits since the last tag. Add anything missing from [Unreleased] (group under Added / Changed / Fixed / Removed). Skip routine chore(deps) unless security-relevant.

  4. Promote [Unreleased] → [X.Y.Z] - YYYY-MM-DD

    • Use today's date for stable releases.
    • Leave an empty ## [Unreleased] section at the top.
    • Add a compare link immediately after the new section:
      markdown
      [X.Y.Z]: https://github.com/zifeo/lade/compare/v<prev>...vX.Y.Z
    • Previous tag is usually the last stable tag on main (ignore unreleased beta tags unless the user says otherwise).

  5. Writing style (match existing entries):

    • Lead with bold feature name, then PR link ([#NNN](https://github.com/zifeo/lade/pull/NNN)).
    • One line per item; explain why when behavior changes.
    • Categories: Added, Changed, Fixed, Removed (omit empty categories).

Version bump

Use scripts/set-version.sh, not a bare cargo set-version and not a hand edit of Cargo.toml:

bash
bash scripts/set-version.sh X.Y.Z
cargo test --workspace --locked

The script runs cargo set-version --workspace (lade, lade-sdk, age-plugin-lade, path deps). Run tests (same as CI) to refresh Cargo.lock and verify the bump.

If cargo set-version is missing: cargo install cargo-edit. CI beta bumps use bash scripts/set-version.sh --bump beta.

GitHub release notes

The tag workflow publishes the matching CHANGELOG.md section with parse-changelog. Write that section before tagging. If the GitHub release already exists, its title and notes stay as first published. A crashed job is recovered by re-running that job. An asset already on the release is left in place.

Checklist

- [ ] `[Unreleased]` promoted to `[X.Y.Z]` with correct date
- [ ] Compare link added (`v<prev>...vX.Y.Z`)
- [ ] All commits since last tag accounted for
- [ ] `bash scripts/set-version.sh X.Y.Z` applied (no `-beta` left unless intentional)
- [ ] GitHub release tag `vX.Y.Z` is the APM pin (`zifeo/lade#vX.Y.Z`)
- [ ] `cargo test --workspace --locked` passes

© zifeo, MPL-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 .cursor/skills/lade-release of zifeo/lade.

Open the folder on GitHubat commit 429000b

Compare with similar skills

Lade 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.

Lade Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lade Release this skillzifeo/lade133—~749Automated safety check: PassMPL-2.0
Worktrunk Release Workflowmax-sixty/worktrunk9.1k—~6.9kAutomated safety check: PassCustom licence
Create Release Checklistsoftware-mansion/smelter734—~1.9kAutomated safety check: NotesCustom licence
Mariadb Operator Release Notesmariadb-operator/mariadb-operator1k—~3.3kAutomated safety check: PassApache-2.0
Release VersionGOODBOY008/r-shell153—~4kAutomated safety check: PassMIT
Niubashunixwin/niubash158—~2.1kAutomated safety check: PassMIT

Similar skills

  • 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.

    9.1k GitHub stars~6.9k tokensUpdated today
    DevelopmentAuto-check passed

  • Create Release Checklist

    software-mansion/smelter

    Generate a GitHub release-checklist issue for a full (non-RC) release of the Smelter server and/or the TypeScript SDK.

    734 GitHub stars~1.9k tokensUpdated yesterday
    DevelopmentAuto-check: notes

  • Mariadb Operator Release Notes

    mariadb-operator/mariadb-operator

    Create the release notes and upgrade guide for a mariadb-operator release.

    1k GitHub stars~3.3k tokensUpdated 2 days ago
    DevelopmentAuto-check passed

  • Release Version

    GOODBOY008/r-shell

    Release a new r-shell version and create a published GitHub release with contributor credits.

    153 GitHub stars~4k tokensUpdated today
    DevelopmentAuto-check passed

  • Niubash

    unixwin/niubash

    Run Windows tasks in Niubash, the GNU Bash-compatible Windows-native shell.

    158 GitHub stars~2.1k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

  • Beava PR Review

    beava-dev/beava

    Reviews a beava PR diff for real bugs, beava-specific architectural invariants, and AI-generated "slop" patterns (hollow code, phantom imports, inflated comments, disconnected pipelines).

    138 GitHub stars~2.1k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

More from zifeo/lade

  • Finalize

    zifeo/lade

    Finalize a merge request: rebase onto main, run bugs, simplify, and specs in parallel, apply, then refactor last.

    133 GitHub stars~1k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Lade Release

What does Lade Release do?

Prepare a Lade release: update CHANGELOG.md and bump crate versions with cargo set-version. Lade Release is an agent skill from zifeo/lade.md and bump crate versions with cargo set-version.

When should I use Lade Release?

Lade Release fits situations like: cutting a release; publishing to GitHub Releases; finalizing the changelog before a version bump.

How do I install Lade Release in Claude Code?

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

How do I install Lade Release in Codex?

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

Can I use Lade 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 zifeo/lade --skill lade-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/lade-release, .gemini/skills/lade-release, .github/skills/lade-release and .opencode/skills/lade-release in your project.

What does Lade Release need to run?

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

Does Lade Release access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Lade 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. Review the folder before installing.

What licence does Lade Release use?

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

How many tokens does Lade Release use?

About 749 tokens (SKILL.md is roughly 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 Lade Release?

Skills that share tags, products or a category with Lade Release: Worktrunk Release Workflow (max-sixty/worktrunk, 9.1k stars), Create Release Checklist (software-mansion/smelter, 734 stars), Mariadb Operator Release Notes (mariadb-operator/mariadb-operator, 1k stars) and Release Version (GOODBOY008/r-shell, 153 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Lade Release?

zifeo (a GitHub user) maintains it in zifeo/lade, which has 133 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 8, 2026.

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