Agent skill

Rocketpy Release

by RocketPy-Team in RocketPy-Team/RocketPy

Cut a new RocketPy release: prepare the version-bump branch, update the changelog and all version references, and guide the PR-to-master + PyPI flow.

MITAuto-check passedDevelopment

Install Rocketpy Release

skills CLI

$ npx skills add RocketPy-Team/RocketPy --skill rocketpy-release -a claude-code

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

GitHub CLI

$ gh skill install RocketPy-Team/RocketPy rocketpy-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/RocketPy-Team/RocketPy.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/rocketpy-release .claude/skills/rocketpy-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/

Paste into Claude Code

Install the "rocketpy-release" agent skill from https://github.com/RocketPy-Team/RocketPy/tree/master/.claude/skills/rocketpy-release into .claude/skills/rocketpy-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketpy-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

$skill-installer install https://github.com/RocketPy-Team/RocketPy/tree/master/.claude/skills/rocketpy-release

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

skills CLI

$ npx skills add RocketPy-Team/RocketPy --skill rocketpy-release -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install RocketPy-Team/RocketPy rocketpy-release --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/RocketPy-Team/RocketPy.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/rocketpy-release .agents/skills/rocketpy-release && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "rocketpy-release" agent skill from https://github.com/RocketPy-Team/RocketPy/tree/master/.claude/skills/rocketpy-release into .agents/skills/rocketpy-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketpy-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.

skills CLI

$ npx skills add RocketPy-Team/RocketPy --skill rocketpy-release -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install RocketPy-Team/RocketPy rocketpy-release --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/RocketPy-Team/RocketPy.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/rocketpy-release .cursor/skills/rocketpy-release && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "rocketpy-release" agent skill from https://github.com/RocketPy-Team/RocketPy/tree/master/.claude/skills/rocketpy-release into .cursor/skills/rocketpy-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketpy-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

$ gemini skills install https://github.com/RocketPy-Team/RocketPy.git --path .claude/skills/rocketpy-release

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add RocketPy-Team/RocketPy --skill rocketpy-release -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install RocketPy-Team/RocketPy rocketpy-release --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/RocketPy-Team/RocketPy.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/rocketpy-release .gemini/skills/rocketpy-release && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "rocketpy-release" agent skill from https://github.com/RocketPy-Team/RocketPy/tree/master/.claude/skills/rocketpy-release into .gemini/skills/rocketpy-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketpy-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.

GitHub CLI

$ gh skill install RocketPy-Team/RocketPy rocketpy-release

Installs 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).

skills CLI

$ npx skills add RocketPy-Team/RocketPy --skill rocketpy-release -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/RocketPy-Team/RocketPy.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/rocketpy-release .github/skills/rocketpy-release && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "rocketpy-release" agent skill from https://github.com/RocketPy-Team/RocketPy/tree/master/.claude/skills/rocketpy-release into .github/skills/rocketpy-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketpy-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.

skills CLI

$ npx skills add RocketPy-Team/RocketPy --skill rocketpy-release -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install RocketPy-Team/RocketPy rocketpy-release --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/RocketPy-Team/RocketPy.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/rocketpy-release .opencode/skills/rocketpy-release && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "rocketpy-release" agent skill from https://github.com/RocketPy-Team/RocketPy/tree/master/.claude/skills/rocketpy-release into .opencode/skills/rocketpy-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "rocketpy-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: rocketpy-release
GitHub stars: 1.1k
Token cost: ~1.3k tokens
SKILL.md length: 522 words
Files: 1
Skills in repo: 1
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Cut a new RocketPy release: prepare the version-bump branch, update the changelog and all version references, and guide the PR-to-master + PyPI flow.

Works in 4 steps: Create the release branch → The version-bump commit → Push and hand off the PR → …
The user wants to release a new version (e.g
SKILL.md covers Branching model, Before you start — gather state, Step 1 — Create the release… and Step 2 — The version-bump commit, plus 3 more sections
Calls git and pip

What it does

Rocketpy Release is an agent skill from RocketPy-Team/RocketPy. Cut a new RocketPy release: prepare the version-bump branch, update the changelog and all version references, and guide the PR-to-master + PyPI flow. Use when the user wants to release a new version (e.g. "release v1.13", "fazer um release", "bump version and cut a release", "REL PR").

Its SKILL.md is about 1.3k 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 Python and GitHub. The repository describes itself as: Next generation High-Power Rocketry 6-DOF Trajectory Simulation. The licence is MIT.

When your agent uses it

The user wants to release a new version (e.g
Tasks that involve Changelog and release notes

Example prompts

“release v1.13”
“fazer um release”
“bump version and cut a release”
“/rocketpy-release”

Requirements

Python 3

Workflow steps

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

Create the release branch
The version-bump commit
Push and hand off the PR
After the PR merges (guide the human)

What it can do on your machine

Read from SKILL.md and the folder at commit 9bd6ad3. 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
- pip
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 pip, 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

Rocketpy Release loads about 1.3k tokens when it runs. Until then it costs about 76 tokens; SKILL.md has 522 words of instructions outside code blocks.

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

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 RocketPy-Team/RocketPy at commit 9bd6ad3, republished under its MIT licence (© RocketPy-Team). 522 words, ~1,282 tokens.

Download SKILL.mdSave it as .claude/skills/rocketpy-release/SKILL.md (or your agent's skills folder).

name: rocketpy-release
description: Cut a new RocketPy release: prepare the version-bump branch, update the changelog and all version references, and guide the PR-to-master + PyPI flow. Use when the user wants to release a new version (e.g. "release v1.13", "fazer um release", "bump version and cut a release", "REL PR").

RocketPy Release

Prepare and guide a RocketPy version release following the team's established REL: pattern. This skill prepares the branch and the version-bump commit; the human opens the PR and publishes the GitHub Release themselves.

Branching model

RocketPy uses develop (integration) and master (released). All feature/fix work lands on develop. A release promotes develop → master.

Since v1.12.0 the team uses a single streamlined PR (see PR #935): one rel/vX.Y.Z branch — created off develop, with the version already bumped — opened straight to master. (Older releases used three PRs; do NOT revive that.)

PyPI is published automatically by .github/workflows/publish-to-pypi.yml when a GitHub Release is published (on: release: [published]). Creating the release/tag in the GitHub UI is the final manual trigger.

Before you start — gather state

Run these and confirm with the user:

bash

git fetch origin
grep -m1 '^version' pyproject.toml                 # current version
git show origin/master:pyproject.toml | grep -m1 '^version'   # released version
git rev-list --left-right --count origin/master...origin/develop  # ahead/behind
git tag --sort=-creatordate | head -5              # last tags

Confirm the target version (semver: MAJOR.MINOR.PATCH) with the user before touching files. Never guess the number.

Step 1 — Create the release branch

Branch off the latest develop:

bash

git checkout develop && git pull origin develop
git checkout -b rel/vX.Y.Z

Step 2 — The version-bump commit

Update every version reference. These have been missed before (e.g. installation.rst sat stale at 1.11.0 through 1.12.x) — check all of them:

File	What to change
`pyproject.toml`	`version = "X.Y.Z"`
`docs/conf.py`	`release = "X.Y.Z"` and `copyright = "<year>, RocketPy Team"`
`docs/user/installation.rst`	`pip install rocketpy==X.Y.Z`
`CHANGELOG.md`	see below

Sanity-sweep for any other stragglers (ignore .venv):

bash

grep -rn "<OLD_VERSION>" --include=*.py --include=*.toml --include=*.rst . \
  | grep -v '.venv'

CHANGELOG.md

The changelog [Unreleased] section is auto-populated on every merge to develop by .github/workflows/changelog.yml, so entries should already be present. To release:

Rename the current ## [Unreleased] - yyyy-mm-dd header to ## [vX.Y.Z] - YYYY-MM-DD (today's date).

Insert a fresh empty [Unreleased] block above it, preserving the template comment and empty subsections:

markdown

## [Unreleased] - yyyy-mm-dd

<!-- These are the changes that were not released yet, please add them correctly.
Attention: The newest changes should be on top -->

### Added

### Changed

### Fixed

Add a Changed entry to the released section for the bump itself: - REL: bumps up rocketpy version to X.Y.Z [#PR](https://github.com/RocketPy-Team/RocketPy/pull/PR) (fill the PR number after the PR is opened, or leave a placeholder to edit).
Prune obvious noise if the maintainer wants (tests, CI, merge commits are not meant to be in the changelog per the file's own header comment).

Show full SKILL.md (198 more words)Show less

Commit

Match the historical message style (REL: bump version to X.Y.Z):

bash

git add pyproject.toml docs/conf.py docs/user/installation.rst CHANGELOG.md
git commit -m "REL: bumps up rocketpy version to X.Y.Z"

Keep it to one bump commit. Do not include unrelated changes.

Step 3 — Push and hand off the PR

bash

git push -u origin rel/vX.Y.Z

Stop here and let the human open the PR (team preference — they open it themselves). Give them the ready-to-use details:

Base: master ← Compare: rel/vX.Y.Z
Title: REL: vX.Y.Z (or Rel/vX.Y.Z)
Body: summarize the highlights; note the single-PR-to-master approach.

Step 4 — After the PR merges (guide the human)

Sync master back into develop so develop carries the new version and the merge history. Historically a PR titled like MNT: update develop to release vX.Y.Z, base develop ← compare master.
Create the GitHub Release in the UI: new tag vX.Y.Z targeting master, title vX.Y.Z, paste the changelog section as notes, Publish. → This triggers publish-to-pypi.yml and ships to PyPI.
Verify the PyPI publish workflow succeeded and the new version is live.

Guardrails

Only prepare the branch + bump commit. Do not open the PR or publish the release unless the user explicitly asks — they do those steps themselves.
Confirm the target version with the user before editing.
Base the PR on master, not develop.
One clean REL: commit; no unrelated edits.

Files

Just SKILL.md in .claude/skills/rocketpy-release of RocketPy-Team/RocketPy.

Open the folder on GitHubat commit 9bd6ad3

Compare with similar skills

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

Rocketpy Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Rocketpy Release this skillRocketPy-Team/RocketPy	1.1k	—	~1.3k	Automated safety check: Pass	MIT	yesterday
pybind11 Release Publicationpybind/pybind11	18k	—	~2.5k	Automated safety check: Pass	Custom licence	today
EverOS Release WorkflowEverMind-AI/EverOS	13k	—	~1.3k	Automated safety check: Pass	Apache-2.0	today
Pre ReleaseZhuoZhuoCrayon/throttled-py	651	—	~1.1k	Automated safety check: Pass	MIT	1 mo ago
Releasezmievsa/cadwyn	309	—	~522	Automated safety check: Pass	MIT	today
Skills Constitutionjiabaobei/skills-constitution	231	—	~5.6k	Automated safety check: Pass	MIT	4 days ago

Similar skills

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.
18k GitHub stars~2.5k tokensUpdated today
DevelopmentAuto-check passed
EverOS Release Workflow
EverMind-AI/EverOS
Walks through cutting a versioned everos release: bump the version, update the changelog, tag it, and review the drafted GitHub Release page before publishing.
13k GitHub stars~1.3k tokensUpdated today
DevelopmentAuto-check passed
Pre Release
ZhuoZhuoCrayon/throttled-py
Automates release preparation for throttled-py. An agent skill from ZhuoZhuoCrayon/throttled-py.
651 GitHub stars~1.1k tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Release
zmievsa/cadwyn
Prepare and publish Cadwyn releases. An agent skill from zmievsa/cadwyn.
309 GitHub stars~522 tokensUpdated today
DevelopmentAuto-check passed
Skills Constitution
jiabaobei/skills-constitution
当 Agent 接到专业任务（编码/爬虫/文件操作/API调用/数据分析/文档/部署/推送等）时，强制先查记忆层和技能索引，有匹配必用、无匹配必搜、答复时自动推荐（排除已装）。用于防止 Agent 跳过技能直接硬扛通用能力。跨平台通用（WorkBuddy/Claude/ChatGPT/Cursor/Gemini 等 20+ 框架）。完整版本史见 CHANGELOG.md。
231 GitHub stars~5.6k tokensUpdated 4 days ago
DevelopmentAuto-check passed
Changelog Draft Generator
warpdotdev/warp
Builds a reviewable changelog draft from the PRs merged between two release cuts, with contributor attribution and Markdown and JSON outputs.
65k GitHub starsUsed in 1 repo~3.1k tokens
DevelopmentAuto-check passed

Works with

Questions about Rocketpy Release

What does Rocketpy Release do?

Cut a new RocketPy release: prepare the version-bump branch, update the changelog and all version references, and guide the PR-to-master + PyPI flow. Rocketpy Release is an agent skill from RocketPy-Team/RocketPy. Cut a new RocketPy release: prepare the version-bump branch, update the changelog and all version references, and guide the PR-to-master + PyPI flow.

When should I use Rocketpy Release?

Rocketpy Release fits situations like: the user wants to release a new version (e.g; tasks that involve Changelog and release notes.

How do I install Rocketpy Release in Claude Code?

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

How do I install Rocketpy Release in Codex?

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

Can I use Rocketpy 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 RocketPy-Team/RocketPy --skill rocketpy-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/rocketpy-release, .gemini/skills/rocketpy-release, .github/skills/rocketpy-release and .opencode/skills/rocketpy-release in your project.

What does Rocketpy Release need to run?

Going by SKILL.md and its folder, Rocketpy Release needs the command-line tools its instructions call (git and pip). Our summary lists: Python 3.

Does Rocketpy Release access the network?

SKILL.md contains no URLs. Its commands use git and pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Rocketpy 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 Rocketpy Release use?

Rocketpy 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 Rocketpy Release use?

About 1.3k tokens (SKILL.md is roughly 5.1k 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 Rocketpy Release?

Skills that share tags, products or a category with Rocketpy Release: pybind11 Release Publication (pybind/pybind11, 18k stars), EverOS Release Workflow (EverMind-AI/EverOS, 13k stars), Pre Release (ZhuoZhuoCrayon/throttled-py, 651 stars) and Release (zmievsa/cadwyn, 309 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Rocketpy Release?

RocketPy-Team (a GitHub organization) maintains it in RocketPy-Team/RocketPy, which has 1,090 GitHub stars. The repository was last updated on October 5, 2026.

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

Install Rocketpy Release

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

RocketPy Release

Branching model

Before you start — gather state

Step 1 — Create the release branch

Step 2 — The version-bump commit

CHANGELOG.md

Commit

Step 3 — Push and hand off the PR

Step 4 — After the PR merges (guide the human)

Guardrails

Files

Compare with similar skills

Similar skills

pybind11 Release Publication

EverOS Release Workflow

Pre Release

Release

Skills Constitution

Changelog Draft Generator

Related

Questions about Rocketpy Release