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

Release

by LennartHennigs in LennartHennigs/ESPRotary

Cut a new ESPRotary release — suggests version bump based on change type, updates version files and CHANGELOG, commits, tags, pushes, creates a GitHub release, and publishes to PlatformIO

MITAuto-check passedDevelopment

Install Release

skills CLI
$ npx skills add LennartHennigs/ESPRotary --skill release -a claude-code

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

GitHub CLI
$ gh skill install LennartHennigs/ESPRotary 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/LennartHennigs/ESPRotary.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
188
Token cost
~629 tokens
SKILL.md length
278 words
Files
1
Skills in repo
4
Repo updated
First seen
Licence
MIT

At a glance

Cut a new ESPRotary release — suggests version bump based on change type, updates version files and CHANGELOG, commits, tags, pushes, creates a GitHub release, and publishes to PlatformIO

  • Works in 6 steps: Determine the version → Update version files → Finalize CHANGELOG → …
  • Tasks that involve Changelog and release notes
  • SKILL.md covers Step 1: Determine the version, Step 2: Update version files, Step 3: Finalize CHANGELOG and Step 4: Commit, tag, push, plus 2 more sections
  • Calls git and gh

What it does

Release is an agent skill from LennartHennigs/ESPRotary. Cut a new ESPRotary release — suggests version bump based on change type, updates version files and CHANGELOG, commits, tags, pushes, creates a GitHub release, and publishes to PlatformIO

Its SKILL.md is about 630 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 Embedded systems. It works with ESP32 and GitHub. The repository describes itself as: Arduino/ESP library to simplify reading rotary encoder data. The licence is MIT.

When your agent uses it

  • Tasks that involve Changelog and release notes
  • Tasks that involve Embedded systems

Example prompts

  • “/release”

Workflow steps

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

  1. Determine the version
  2. Update version files
  3. Finalize CHANGELOG
  4. Commit, tag, push
  5. Create GitHub release
  6. Publish to PlatformIO registry

What it can do on your machine

Read from SKILL.md and the folder at commit 2d029ba. 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
    • gh

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

  • Network

    No URLs in SKILL.md. Its commands use git and gh, 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 629 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 278 words of instructions outside code blocks.

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

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 LennartHennigs/ESPRotary at commit 2d029ba, republished under its MIT licence (© LennartHennigs). 278 words, ~629 tokens.

Download SKILL.mdSave it as .claude/skills/release/SKILL.md (or your agent's skills folder).
name
release
description
Cut a new ESPRotary release — suggests version bump based on change type, updates version files and CHANGELOG, commits, tags, pushes, creates a GitHub release, and publishes to PlatformIO

Cut a new ESPRotary release. Follow these steps exactly:

Step 1: Determine the version

Read library.json to get the current version.

Read the ## Unreleased section of CHANGELOG.md to understand what changed.

If $ARGUMENTS is provided, use that as the new version. Otherwise:

  • Classify the unreleased changes:
    • Major (x.0.0): breaking API changes, removed functions, changed signatures
    • Minor (x.y.0): new public functions, new features, new examples
    • Patch (x.y.z): bug fixes, internal changes, test additions, docs
  • Suggest the new version with a one-line explanation of your reasoning
  • Use AskUserQuestion to ask the user to confirm the suggested version or provide a different one

Step 2: Update version files

Update the version number in both (they must match):

  • library.json — the "version" field
  • library.properties — the version= line

Step 3: Finalize CHANGELOG

In CHANGELOG.md:

  • Rename ## Unreleased to ## [x.y.z] - YYYY-MM-DD (today's date, new version)
  • Add a fresh empty ## Unreleased heading above it
  • Use American English spelling

Step 4: Commit, tag, push

ESPRotary tags use the bare version number — no v prefix (e.g. 2.2.1).

bash
git add library.json library.properties CHANGELOG.md
git commit -m "release: bump version to X.Y.Z"
git tag X.Y.Z
git push && git push --tags

Step 5: Create GitHub release

Extract the release notes for this version from the CHANGELOG (the bullets under ## [x.y.z]), then run:

bash
gh release create X.Y.Z --target master --title "X.Y.Z" --notes "<changelog bullets>" --latest

The Arduino Library Manager picks up the new tag automatically from GitHub — no separate step needed there.

Step 6: Publish to PlatformIO registry

Requires pio account login first (interactive — the maintainer must do this; verify with pio account show).

bash
pio pkg publish --no-interactive

pio pkg publish packages the current working directory (the /.pio/ build dir and .git are excluded automatically) and uses the version from library.json. A published version is immutable — it can only be published once, so make sure the release is correct first.

Confirm each step succeeded and report which registries were updated.

© LennartHennigs, 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 LennartHennigs/ESPRotary.

Open the folder on GitHubat commit 2d029ba

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 skillLennartHennigs/ESPRotary188—~629Automated safety check: PassMIT
ReleaseLennartHennigs/Button2565—~519Automated safety check: PassMIT
Cutting A ReleaseTriliumNext/Trilium38k—~3.2kAutomated safety check: PassAGPL-3.0
Mole CLI Release Flowtw93/Mole70k—~2.6kAutomated safety check: PassGPL-3.0
Draft Release Notesjamiepine/voicebox57k—~941Automated safety check: PassMIT
Mole Release Notes Publishertw93/Mole70k—~1.9kAutomated safety check: PassGPL-3.0

Similar skills

  • Release

    LennartHennigs/Button2

    Cut a new Button2 release — suggests version bump based on change type, updates version files and CHANGELOG, commits, tags, pushes, creates a GitHub release, and publishes to PlatformIO

    565 GitHub stars~519 tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

  • Cutting A Release

    TriliumNext/Trilium

    A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.

    38k GitHub stars~3.2k tokensUpdated today
    DevelopmentAuto-check passed

  • Mole CLI Release Flow

    tw93/Mole

    Runbook for assessing and executing a Mole CLI release: distribution channels, pre-flight checks, capital-V tags, build artifacts and the handoff to curated release notes.

    70k GitHub stars~2.6k 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 3 days ago
    DevelopmentAuto-check passed

  • Mole Release Notes Publisher

    tw93/Mole

    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

  • Release Bump

    jamiepine/voicebox

    Ends a release cycle by moving the Unreleased changelog notes under a dated version heading, bumping version files with bumpversion and tagging the commit.

    57k GitHub stars~1.1k tokensUpdated 3 days ago
    DevelopmentAuto-check passed

More from LennartHennigs/ESPRotary

  • Commit

    LennartHennigs/ESPRotary

    Stage and commit current changes for ESPRotary — checks for needed CHANGELOG/README/CLAUDE.md updates, creates a branch if on master, writes a commit message, and commits

    188 GitHub stars~590 tokensUpdated 2 mo ago
    Auto-check passed

  • Readme

    LennartHennigs/ESPRotary

    Audit README.md against the current ESPRotary API and recent CHANGELOG entries, then apply any needed updates

    188 GitHub stars~417 tokensUpdated 2 mo ago
    Auto-check passed

  • Compile

    LennartHennigs/ESPRotary

    Compile ESPRotary examples with arduino-cli to verify they build.

    188 GitHub stars~329 tokensUpdated 2 mo ago
    Auto-check passed

Works with

Categories

Questions about Release

What does Release do?

Cut a new ESPRotary release — suggests version bump based on change type, updates version files and CHANGELOG, commits, tags, pushes, creates a GitHub release, and publishes to PlatformIO. Release is an agent skill from LennartHennigs/ESPRotary.

When should I use Release?

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

How do I install Release in Claude Code?

Run `npx skills add LennartHennigs/ESPRotary --skill release -a claude-code`. Or copy the skill folder (.claude/skills/release in LennartHennigs/ESPRotary) 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 LennartHennigs/ESPRotary --skill release -a codex`. Or copy the skill folder (.claude/skills/release in LennartHennigs/ESPRotary) 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 LennartHennigs/ESPRotary --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 gh).

Does Release access the network?

SKILL.md contains no URLs. Its commands use git and gh, 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 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 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 629 tokens (SKILL.md is roughly 2.5k 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: Release (LennartHennigs/Button2, 565 stars), Cutting A Release (TriliumNext/Trilium, 38k stars), Mole CLI Release Flow (tw93/Mole, 70k stars) and Draft Release Notes (jamiepine/voicebox, 57k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Release?

LennartHennigs (a GitHub user) maintains it in LennartHennigs/ESPRotary, which has 188 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on July 27, 2026.

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