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.
Walks a maintainer through publishing a pybind11 release after the preparation PR merges, with preflight checks, confirmations before each push and a GitHub release.
Install pybind11 Release Publication
$ npx skills add pybind/pybind11 --skill publish-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pybind/pybind11 publish-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/pybind/pybind11.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/publish-release .claude/skills/publish-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 "publish-release" agent skill from https://github.com/pybind/pybind11/tree/master/.agents/skills/publish-release into .claude/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-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/pybind/pybind11/tree/master/.agents/skills/publish-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 pybind/pybind11 --skill publish-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pybind/pybind11 publish-release --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pybind/pybind11.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/publish-release .agents/skills/publish-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 "publish-release" agent skill from https://github.com/pybind/pybind11/tree/master/.agents/skills/publish-release into .agents/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-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 pybind/pybind11 --skill publish-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pybind/pybind11 publish-release --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pybind/pybind11.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/publish-release .cursor/skills/publish-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 "publish-release" agent skill from https://github.com/pybind/pybind11/tree/master/.agents/skills/publish-release into .cursor/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-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/pybind/pybind11.git --path .agents/skills/publish-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 pybind/pybind11 --skill publish-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pybind/pybind11 publish-release --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pybind/pybind11.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/publish-release .gemini/skills/publish-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 "publish-release" agent skill from https://github.com/pybind/pybind11/tree/master/.agents/skills/publish-release into .gemini/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-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 pybind/pybind11 publish-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 pybind/pybind11 --skill publish-release -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/pybind/pybind11.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/publish-release .github/skills/publish-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 "publish-release" agent skill from https://github.com/pybind/pybind11/tree/master/.agents/skills/publish-release into .github/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-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 pybind/pybind11 --skill publish-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 pybind/pybind11 publish-release --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/pybind/pybind11.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/publish-release .opencode/skills/publish-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 "publish-release" agent skill from https://github.com/pybind/pybind11/tree/master/.agents/skills/publish-release into .opencode/skills/publish-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publish-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
publish-release- GitHub stars
- 18k
- Token cost
- ~2.5k tokens
- SKILL.md length
- 1,404 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Walks a maintainer through publishing a pybind11 release after the preparation PR merges, with preflight checks, confirmations before each push and a GitHub release.
- Works in 6 steps: Preflight → Release branch → Tag → …
- Cutting a pybind11 release after the prepare-release PR has merged
- SKILL.md covers 1. Preflight, 2. Release branch, 3. Tag and 4. Update stable when…, plus 3 more sections
- Calls git, gh and python
What it does
The skill treats `docs/release.rst` as the source of truth and tells the agent to follow that file and update the skill if they disagree. It requires the exact version and the merged release-preparation PR, never inferred from the current checkout, and defines the tag as `v` plus that version, so a release candidate keeps its rc suffix. Before every push, label change and the GitHub release it stops for your explicit confirmation, showing the repository, refs, commit SHA and notes.
Preflight demands a clean tree, upstream remotes that point at the official pybind11 repository, a fetch with tags, and working `gh` authentication with release permissions. The agent checks that the preparation PR merged, records its base and merge commit, and requires the full CI release matrix to have passed on the tested commit. A later commit may be released only with your approval and equivalent CI. It also verifies that the Python version string matches the requested version and is not a development version, along with the version in `include/pybind11/detail/common.h`.
When your agent uses it
- Cutting a pybind11 release after the prepare-release PR has merged
- Verifying CI and version metadata before tagging a release
- Publishing a release candidate with the correct tag
- Retrying an interrupted release from a recorded checkpoint
Example prompts
- “Publish the release for version 3.2.0rc1 now that its preparation PR is merged.”
- “Run the preflight checks for the pending pybind11 release without pushing anything.”
- “Resume the release from the checkpoint I recorded earlier.”
Requirements
- Push access to the official pybind11 repository
- GitHub CLI (`gh`) authenticated with release permissions
- The exact version and the merged release-preparation PR
Workflow steps
6 steps, taken from the step headings in SKILL.md.
- Preflight
- Release branch
- Tag
- Update stable when appropriate
- GitHub release
- Post-release bump ("get back to work")
What it can do on your machine
Read from SKILL.md and the folder at commit 46bfd99. 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:
gitghpython
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
pybind11 Release Publication loads about 2.5k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 1,404 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); 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 1,404 words (~2,488 tokens).
“Source of truth: docs/release.rst. If this skill and that file disagree, follow docs/release.rst and update this skill.”
- name
- publish-release
Files
Just SKILL.md in .agents/skills/publish-release of pybind/pybind11.
Open the folder on GitHubat commit 46bfd99
Compare with similar skills
pybind11 Release Publication 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 |
|---|---|---|---|---|---|---|
| pybind11 Release Publication this skillpybind/pybind11 | 18k | — | ~2.5k | Automated safety check: Pass | Custom licence | |
| Release Bumpjamiepine/voicebox | 57k | — | ~1.1k | Automated safety check: Pass | MIT | |
| Go-Redis Release Preparationredis/go-redis | 22k | — | ~1.1k | Automated safety check: Pass | BSD-2-Clause | |
| Hunk Release Workflowmodem-dev/hunk | 9.5k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Worktrunk Release Workflowmax-sixty/worktrunk | 8.9k | — | ~6.9k | Automated safety check: Pass | Custom licence | |
| Obot Release Notes Drafterobot-platform/obot | 1.1k | — | ~4.5k | Automated safety check: Pass | MIT |
Similar skills
- Official
Go-Redis Release Preparation
redis/go-redis
Prepares a go-redis release locally: picks the next semver, gathers merged PRs, writes the RELEASE-NOTES entry and bumps versions, without publishing.
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.
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.
Obot Release Notes Drafter
obot-platform/obot
Drafts release notes for an upcoming Obot minor release and saves them as an unpublished GitHub draft release, never tagging or publishing.
GreptimeDB Release Notes
GreptimeTeam/greptimedb
Generates a GreptimeDB release changelog with git cliff, subtracts patch PRs already shipped, rebuilds contributors and prepares the docs-repo blog PR.
More from pybind/pybind11
pybind11 Release Preparation
pybind/pybind11
Opens the pybind11 release-preparation pull request: picking the release base, bumping the version in common.h and integrating the changelog, following docs/release.rst.
Related
Categories
Questions about pybind11 Release Publication
What does pybind11 Release Publication do?
Walks a maintainer through publishing a pybind11 release after the preparation PR merges, with preflight checks, confirmations before each push and a GitHub release. rst` as the source of truth and tells the agent to follow that file and update the skill if they disagree. It requires the exact version and the merged release-preparation PR, never inferred from the current checkout, and defines the tag as `v` plus that version, so a release candidate keeps its rc suffix.
When should I use pybind11 Release Publication?
pybind11 Release Publication fits situations like: cutting a pybind11 release after the prepare-release PR has merged; verifying CI and version metadata before tagging a release; publishing a release candidate with the correct tag; retrying an interrupted release from a recorded checkpoint.
How do I install pybind11 Release Publication in Claude Code?
Run `npx skills add pybind/pybind11 --skill publish-release -a claude-code`. Or copy the skill folder (.agents/skills/publish-release in pybind/pybind11) into .claude/skills/publish-release in your project. Claude Code loads it when a task matches its description.
How do I install pybind11 Release Publication in Codex?
Run `npx skills add pybind/pybind11 --skill publish-release -a codex`. Or copy the skill folder (.agents/skills/publish-release in pybind/pybind11) into .agents/skills/publish-release in your project. Codex loads it when a task matches its description.
Can I use pybind11 Release Publication 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 pybind/pybind11 --skill publish-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/publish-release, .gemini/skills/publish-release, .github/skills/publish-release and .opencode/skills/publish-release in your project.
What does pybind11 Release Publication need to run?
Going by SKILL.md and its folder, pybind11 Release Publication needs the command-line tools its instructions call (git, gh and python). Our summary lists: Push access to the official pybind11 repository; GitHub CLI (`gh`) authenticated with release permissions; The exact version and the merged release-preparation PR.
Does pybind11 Release Publication 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 pybind11 Release Publication 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 pybind11 Release Publication use?
pybind11 Release Publication 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 pybind11 Release Publication use?
About 2.5k tokens (SKILL.md is roughly 10k 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 pybind11 Release Publication?
Skills that share tags, products or a category with pybind11 Release Publication: Release Bump (jamiepine/voicebox, 57k stars), Go-Redis Release Preparation (redis/go-redis, 22k stars), Hunk Release Workflow (modem-dev/hunk, 9.5k stars) and Worktrunk Release Workflow (max-sixty/worktrunk, 8.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains pybind11 Release Publication?
pybind (a GitHub organization) maintains it in pybind/pybind11, which has 18,023 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 6, 2026.
Source: pybind/pybind11 on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.