Release

Cut a milestone release: the release issue, the preparation PRs on v2/main (audit, changesets Version Packages, Python CalVer), the pure v2/main to main merge PR with its release ledger, then the GitHub Release a maintainer publishes.

92,088 stars 11,978 forksGit & Code Review

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add modelcontextprotocol/servers --skill release
Manual install
git clone --depth 1 https://github.com/modelcontextprotocol/servers.git /tmp/servers
mkdir -p ~/.claude/skills
cp -r /tmp/servers/.claude/skills/release ~/.claude/skills/release

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Cutting a milestone release

How versions and publishing work, and what to do when a publish fails, is
[`RELEASING.md`](../../../RELEASING.md). This skill is the procedure for one
milestone, start to finish. It is started by name only (`/release`), because a
release is never something to begin by inference.

A release is cut from **`main`**, after the milestone's work has been merged
there from `v2/main`. Nothing publishes from `v2/main`: `release.yml` refuses a
Release whose commit is not on `main`.

**What stays human.** Publishing the GitHub Release and approving the `release`
environment deployments are a maintainer's acts. So is merging any PR. Prepare,
verify and recommend; do not perform those.

## 0. Check this session's instructions first

A release is the longest-running session and the costliest to get wrong, and
it follows this skill and `AGENTS.md` exactly as they were when the session
started. Before step 1, run the staleness check in `AGENTS.md`
**Issue-driven work style** (all work in a worktree freshly cut from
`origin/v2/main`), whatever the `SessionStart` hook printed: the hook ran when
the session began, and this check runs now.

On `STALE`, or a `STALE` line from the `SessionStart` hook, **stop** and ask
for a session started in a fresh worktree. The v2.0.0 release ran its first
three steps on a `release` skill 447 commits out of date (#5167). Re-run the
check after each preparation PR merges, since `v2/main` moves under the
Read the full skill on GitHub

Details

Skill name
release
Path
.claude/skills/release/SKILL.md
Repo updated
18 November 2026

FAQ

What does the Release skill do?

Cut a milestone release: the release issue, the preparation PRs on v2/main (audit, changesets Version Packages, Python CalVer), the pure v2/main to main merge PR with its release ledger, then the GitHub Release a maintainer publishes.

How do I install the Release skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add modelcontextprotocol/servers --skill release. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Release popular?

It lives in modelcontextprotocol/servers, which has 92,088 GitHub stars and 11,978 forks, and is included in 1 curated skill list.

Related skills

Board Ops

92k

modelcontextprotocol/servers

gh recipes for the Servers V2 project board (#43): add an issue's card, move its Status, set or change its Priority, delete a card, and recover from a deleted single-select option. Use when moving a card between columns; when setting Status or Priority; when an option ID is rejected; before editing a board field's options; or when cards lost their Status or Priority.

OtherIn 1 list12k

Client Smoke

92k

modelcontextprotocol/servers

Drive a locally built server with a real client: the Inspector CLI (scripted), the Inspector web UI (through Playwright) and an LLM client. Use when smoke-testing a server change; when calling a tool, reading a resource or getting a prompt from the command line; when choosing a protocol era; or when the Inspector CLI will not connect to, or misreads, a server command.

Testing & QAIn 1 list12k

Issue Create

92k

modelcontextprotocol/servers

Create a tracked issue in this repo end to end — duplicate check, v2 label, type label, server-scope label, milestone, board card, Status and Priority. Use when asked to file, create, open or raise an issue; when picking its labels or its milestone; when checking whether one already exists; or when work discovered mid-task needs an issue of its own.

Skill & Plugin AuthoringIn 1 list12k

Repo Guidance

31k

ComposioHQ/composio

Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK implementation.

Git & Code ReviewIn 1 list5k

PR Flow

92k

modelcontextprotocol/servers

Take an issue through to a PR in this repo and close it out after merge. Use when asked to open, create or submit a PR; when naming a branch; when signing off commits or repairing a missing Signed-off-by; when recording client evidence for a PR; when requesting a Copilot review, answering its comments or deciding whether to run another round; or when closing out after a merge.

Git & Code ReviewIn 1 list12k

Release

22k

screenpipe/screenpipe

Release the screenpipe monorepo. Bumps versions, triggers GitHub Actions for app, CLI, MCP, and JS packages.

Git & Code ReviewIn 1 list2.3k

Browse the most popular Claude skills, all git & code review skills, or write your own with the skills generator.