New: 97,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

Official agent skill

Release

by DataDog in DataDog/lading

Prepare a lading release. An agent skill from DataDog/lading.

OfficialMITAuto-check: notesDevelopment

Install Release

skills CLI
$ npx skills add DataDog/lading --skill release -a claude-code

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

GitHub CLI
$ gh skill install DataDog/lading 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/DataDog/lading.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/

Facts

Skill name
release
GitHub stars
101
Token cost
~465 tokens
SKILL.md length
225 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
MIT

At a glance

Prepare a lading release. An agent skill from DataDog/lading.

  • Works in 7 steps: Determine the next version → Create a release branch → Update CHANGELOG.md → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers 1. Determine the next version, 2. Create a release branch, 3. Update CHANGELOG.md and 4. Bump version in Cargo.toml, plus 3 more sections
  • Calls git and cargo

What it does

Release is an agent skill from DataDog/lading, published by the product's own GitHub organization. Prepare a lading release. Updates CHANGELOG.md, bumps version in Cargo.toml, updates Cargo.lock, commits, and creates a PR.

Its SKILL.md is about 470 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. It works with Rust and Git. The repository describes itself as: A suite of data generation and load testing tools. The licence is MIT.

When your agent uses it

  • Tasks that involve Changelog and release notes

Example prompts

  • “/release”

Requirements

  • Pre-approved tools (allowed-tools): Read, Edit, Bash, AskUserQuestion

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Determine the next version
  2. Create a release branch
  3. Update CHANGELOG.md
  4. Bump version in Cargo.toml
  5. Update Cargo.lock
  6. Commit and create PR
  7. Tag after merge

What it can do on your machine

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

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Edit
    • Bash
    • AskUserQuestion

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • cargo

    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

Release loads about 465 tokens when it runs. Until then it costs about 33 tokens; SKILL.md has 225 words of instructions outside code blocks.

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

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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Edit, Bash, AskUserQuestion

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 DataDog/lading at commit a7bb0ea, republished under its MIT licence (© DataDog). 225 words, ~465 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Prepare a lading release. Updates CHANGELOG.md, bumps version in Cargo.toml, updates Cargo.lock, commits, and creates a PR.
allowed-tools
Read, Edit, Bash, AskUserQuestion

Release process for lading

1. Determine the next version

  • Read lading/Cargo.toml and CHANGELOG.md to find the current version and unreleased changes.
  • If the user hasn't specified a version, suggest one based on semver:
    • Breaking changes in the unreleased section -> bump minor (we're pre-1.0).
    • Otherwise bump patch.
  • Confirm the version with the user before proceeding.

2. Create a release branch

  • Create a branch from main: git checkout -b prepare-release-v<version>

3. Update CHANGELOG.md

  • Read CHANGELOG.md.
  • Insert a new ## Unreleased header (with empty subsections) above the current unreleased content.
  • Rename the existing unreleased content block to ## [<version>].
  • Ensure there is a blank line between the new empty ## Unreleased and ## [<version>].

4. Bump version in Cargo.toml

  • Edit lading/Cargo.toml to set version = "<new_version>".

5. Update Cargo.lock

  • Run cargo check to propagate the version change into the lockfile without re-resolving all dependencies.

6. Commit and create PR

  • Stage CHANGELOG.md, lading/Cargo.toml, and Cargo.lock.
  • Commit with message: release: v<version>
  • Push the branch and create a PR targeting main.

7. Tag after merge

  • After the PR is merged, remind the user to tag the merge commit on main:
    • git checkout main && git pull
    • git tag -a v<version> -m "v<version>"
    • git push origin v<version>
  • NEVER use git push --tags — always push exactly one tag at a time.
  • The release.yml GitHub Actions workflow will automatically create a GitHub Release from the tag, pulling notes from CHANGELOG.md.

© DataDog, MIT. 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 .claude/skills/release of DataDog/lading.

Open the folder on GitHubat commit a7bb0ea

Compare with similar skills

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.

Release compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Release this skillDataDog/lading101—~465Automated safety check: NotesMIT
Worktrunk Release Workflowmax-sixty/worktrunk8.9k—~6.9kAutomated safety check: PassCustom licence
Releasexin2017338/lynx-proxy502—~1.1kAutomated safety check: PassMIT
Prepare Releasefrozenlib/parse-display193—~1.3kAutomated safety check: PassApache-2.0
Releaseyicheng47/runner269—~1.8kAutomated safety check: PassMIT
Release Crater3bl-org/r3bl-open-core485—~2.4kAutomated safety check: PassApache-2.0

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.

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

  • Release

    xin2017338/lynx-proxy

    Publish a new release version of Lynx Proxy. An agent skill from xin2017338/lynx-proxy.

    502 GitHub stars~1.1k tokensUpdated 22 days ago
    DevelopmentAuto-check passed

  • Prepare Release

    frozenlib/parse-display

    Prepare parse-display release changes before publishing with a Rust Cargo script when nightly Cargo is available.

    193 GitHub stars~1.3k tokensUpdated 3 days ago
    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…

    269 GitHub stars~1.8k tokensUpdated today
    DevelopmentAuto-check passed

  • Release Crate

    r3bl-org/r3bl-open-core

    Publish a crate release to crates.io with changelog, standalone release notes, git tag, and GitHub release.

    485 GitHub stars~2.4k tokensUpdated yesterday
    DevelopmentAuto-check passed

  • Release Management

    termide/termide

    Prepare and publish a project release with version updates, changelog generation, tagging, and validation

    171 GitHub stars~6.8k tokensUpdated yesterday
    DevelopmentAuto-check passed

More from DataDog/lading

  • Lading Optimize Find Target

    DataDog/lading

    Official

    Finds a valid optimization target in lading. An agent skill from DataDog/lading.

    101 GitHub stars~1.5k tokensUpdated 7 days ago
    Auto-check: notes

  • Lading Optimize Hunt

    DataDog/lading

    Official

    Coordinates optimization attempts. An agent skill from DataDog/lading.

    101 GitHub stars~1k tokensUpdated 7 days ago
    Auto-check passed

  • Lading Optimize Review

    DataDog/lading

    Official

    Reviews optimization patches using a 5-persona peer review system.

    101 GitHub stars~1.9k tokensUpdated 7 days ago
    Auto-check passed

  • Lading Optimize Submit

    DataDog/lading

    Official

    Full optimization workflow with git branch creation, commits, and optional PR.

    101 GitHub stars~837 tokensUpdated 7 days ago
    Auto-check passed

  • Lading Preflight

    DataDog/lading

    Official

    Environment validation checklist. An agent skill from DataDog/lading.

    101 GitHub stars~668 tokensUpdated 7 days ago
    Auto-check: notes

Works with

Categories

Questions about Release

What does Release do?

Prepare a lading release. An agent skill from DataDog/lading. Release is an agent skill from DataDog/lading, published by the product's own GitHub organization. Prepare a lading release.

When should I use Release?

Release fits situations like: tasks that involve Changelog and release notes.

How do I install Release in Claude Code?

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

How do I install Release in Codex?

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

Can I use 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 DataDog/lading --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 Release need to run?

Going by SKILL.md and its folder, Release needs the command-line tools its instructions call (git and cargo). Its frontmatter pre-approves these tools: Read, Edit, Bash, AskUserQuestion.

Does 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 Release safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Release use?

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

How many tokens does Release use?

About 465 tokens (SKILL.md is roughly 1.9k 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 Release?

Skills that share tags, products or a category with Release: Worktrunk Release Workflow (max-sixty/worktrunk, 8.9k stars), Release (xin2017338/lynx-proxy, 502 stars), Prepare Release (frozenlib/parse-display, 193 stars) and Release (yicheng47/runner, 269 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

DataDog (a GitHub organization, an official publisher) maintains it in DataDog/lading, which has 101 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on September 30, 2026.

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