Git Workflow and Versioning
addyosmani/agent-skills
Sets git habits for every change: short-lived branches, atomic commits with descriptive messages, clean pull requests, plus versioning, tagging and changelogs for releases.
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.
Install pybind11 Release Preparation
$ npx skills add pybind/pybind11 --skill prepare-release -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install pybind/pybind11 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/pybind/pybind11.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/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/pybind/pybind11/tree/master/.agents/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/pybind/pybind11/tree/master/.agents/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 pybind/pybind11 --skill prepare-release -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install pybind/pybind11 prepare-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/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/pybind/pybind11/tree/master/.agents/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 pybind/pybind11 --skill prepare-release -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install pybind/pybind11 prepare-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/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/pybind/pybind11/tree/master/.agents/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/pybind/pybind11.git --path .agents/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 pybind/pybind11 --skill prepare-release -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install pybind/pybind11 prepare-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/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/pybind/pybind11/tree/master/.agents/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 pybind/pybind11 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 pybind/pybind11 --skill prepare-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/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/pybind/pybind11/tree/master/.agents/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 pybind/pybind11 --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 pybind/pybind11 prepare-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/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/pybind/pybind11/tree/master/.agents/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
- 18k
- Token cost
- ~1.7k tokens
- SKILL.md length
- 906 words
- Files
- 1
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
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.
- Works in 4 steps: Preflight → Version bump → Changelog → …
- Starting a pybind11 release by opening the release-preparation PR
- SKILL.md covers 1. Preflight, 2. Version bump, 3. Changelog and 4. Commit and PR, plus 1 more section
- Calls git, gh and uvx
What it does
The source of truth is `docs/release.rst`, and the skill defers to it on any disagreement. The argument is the canonical version, either a final release or a release candidate, beta or alpha with a serial between 1 and 15. Without an argument, the agent proposes the next version from the `PYBIND11_VERSION_*` macros and confirms it, and the tag is `v` followed by that exact version. It must confirm the version and release base before editing and pause again before pushing or opening the PR, while everything else may proceed on its own.
Preflight requires a clean tree, checks that the `upstream` remote is the official `pybind/pybind11` repository and fetches with `--prune --tags`. The PR base is chosen from the release line: `master` when the release comes from the current line, or an existing maintained-line branch when `master` has moved on, with the base SHA shown for approval. A fresh branch is cut from the explicit remote ref, and `gh auth status`, release permissions and `nox` are checked. The version bump edits only `include/pybind11/detail/common.h`, and `publish-release` follows after the merge.
When your agent uses it
- Starting a pybind11 release by opening the release-preparation PR
- Bumping the version macros for a release candidate or final release
- Choosing between master and a maintained release branch as the PR base
Example prompts
- “Prepare the next pybind11 release candidate and propose the version before editing anything.”
- “Which base branch should the release-preparation PR target for a patch release on an older line?”
- “Bump the version macros in common.h for a final release and integrate the changelog.”
Requirements
- Git with an `upstream` remote for pybind/pybind11
- The GitHub CLI (`gh`) with release permissions
- `nox` or `uvx nox`
Workflow steps
4 steps, taken from the step headings in SKILL.md.
- Preflight
- Version bump
- Changelog
- Commit and PR
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:
gitghuvx
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, gh and uvx, 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 Preparation loads about 1.7k tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 906 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 906 words (~1,720 tokens).
“Source of truth: docs/release.rst. If this skill and that file disagree, follow docs/release.rst and update this skill.”
- name
- prepare-release
Files
Just SKILL.md in .agents/skills/prepare-release of pybind/pybind11.
Open the folder on GitHubat commit 46bfd99
Compare with similar skills
pybind11 Release Preparation 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 Preparation this skillpybind/pybind11 | 18k | — | ~1.7k | Automated safety check: Pass | Custom licence | |
| Git Workflow and Versioningaddyosmani/agent-skills | 102k | 2 repos | ~3.5k | Automated safety check: Notes | MIT | |
| Skyvern Version BumpSkyvern-AI/skyvern | 23k | — | ~1k | Automated safety check: Notes | AGPL-3.0 | |
| AionUi Version BumpiOfficeAI/AionUi | 33k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Adk Gitgoogle/adk-python | 22k | — | ~1.3k | Automated safety check: Pass | Apache-2.0 | |
| GitHub Fork and PR Submissionjxxghp/MoviePilot | 12k | — | ~1.1k | Automated safety check: Notes | GPL-3.0 |
Similar skills
Skyvern Version Bump
Skyvern-AI/skyvern
Walks through a Skyvern open-source release bump: update the version, rebuild the Python and TypeScript SDKs with Fern, commit, and open a pull request.
AionUi Version Bump
iOfficeAI/AionUi
Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.
- Official
Adk Git
google/adk-python
Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and…
GitHub Fork and PR Submission
jxxghp/MoviePilot
Submits code changes as a GitHub pull request through an isolated Git clone, reusing or creating your fork and pushing only after you confirm the real diff.
ZCF Release Automation
UfoMiao/zcf
Automates a version release with changesets: analyzes code changes, writes a bilingual CHANGELOG, bumps the version and commits through a release branch and pull request.
More from pybind/pybind11
pybind11 Release Publication
pybind/pybind11
Walks a maintainer through publishing a pybind11 release after the preparation PR merges, with preflight checks, confirmations before each push and a GitHub release.
Related
Categories
Questions about pybind11 Release Preparation
What does pybind11 Release Preparation do?
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. rst`, and the skill defers to it on any disagreement. The argument is the canonical version, either a final release or a release candidate, beta or alpha with a serial between 1 and 15.
When should I use pybind11 Release Preparation?
pybind11 Release Preparation fits situations like: starting a pybind11 release by opening the release-preparation PR; bumping the version macros for a release candidate or final release; choosing between master and a maintained release branch as the PR base.
How do I install pybind11 Release Preparation in Claude Code?
Run `npx skills add pybind/pybind11 --skill prepare-release -a claude-code`. Or copy the skill folder (.agents/skills/prepare-release in pybind/pybind11) into .claude/skills/prepare-release in your project. Claude Code loads it when a task matches its description.
How do I install pybind11 Release Preparation in Codex?
Run `npx skills add pybind/pybind11 --skill prepare-release -a codex`. Or copy the skill folder (.agents/skills/prepare-release in pybind/pybind11) into .agents/skills/prepare-release in your project. Codex loads it when a task matches its description.
Can I use pybind11 Release Preparation 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 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 pybind11 Release Preparation need to run?
Going by SKILL.md and its folder, pybind11 Release Preparation needs the command-line tools its instructions call (git, gh and uvx). Our summary lists: Git with an `upstream` remote for pybind/pybind11; The GitHub CLI (`gh`) with release permissions; `nox` or `uvx nox`.
Does pybind11 Release Preparation access the network?
SKILL.md contains no URLs. Its commands use git, gh and uvx, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is pybind11 Release Preparation 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 Preparation use?
pybind11 Release Preparation 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 Preparation use?
About 1.7k tokens (SKILL.md is roughly 6.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 pybind11 Release Preparation?
Skills that share tags, products or a category with pybind11 Release Preparation: Git Workflow and Versioning (addyosmani/agent-skills, 102k stars), Skyvern Version Bump (Skyvern-AI/skyvern, 23k stars), AionUi Version Bump (iOfficeAI/AionUi, 33k stars) and Adk Git (google/adk-python, 22k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains pybind11 Release Preparation?
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.