Official agent skill

Bump And Release

Bump dependency "@typespec/http-client-python" and release new versions for Azure/autorest.python repo.

OfficialMITAuto-check passed

Install Bump And Release

skills CLI

$ npx skills add Azure/autorest.python --skill bump-and-release -a claude-code

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

GitHub CLI

$ gh skill install Azure/autorest.python bump-and-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/Azure/autorest.python.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/bump-and-release .claude/skills/bump-and-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 "bump-and-release" agent skill from https://github.com/Azure/autorest.python/tree/main/.github/skills/bump-and-release into .claude/skills/bump-and-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-and-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/Azure/autorest.python/tree/main/.github/skills/bump-and-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 Azure/autorest.python --skill bump-and-release -a codex

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

GitHub CLI

$ gh skill install Azure/autorest.python bump-and-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/Azure/autorest.python.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/bump-and-release .agents/skills/bump-and-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 "bump-and-release" agent skill from https://github.com/Azure/autorest.python/tree/main/.github/skills/bump-and-release into .agents/skills/bump-and-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-and-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 Azure/autorest.python --skill bump-and-release -a cursor

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

GitHub CLI

$ gh skill install Azure/autorest.python bump-and-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/Azure/autorest.python.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/bump-and-release .cursor/skills/bump-and-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 "bump-and-release" agent skill from https://github.com/Azure/autorest.python/tree/main/.github/skills/bump-and-release into .cursor/skills/bump-and-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-and-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/Azure/autorest.python.git --path .github/skills/bump-and-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 Azure/autorest.python --skill bump-and-release -a gemini-cli

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

GitHub CLI

$ gh skill install Azure/autorest.python bump-and-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/Azure/autorest.python.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/bump-and-release .gemini/skills/bump-and-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 "bump-and-release" agent skill from https://github.com/Azure/autorest.python/tree/main/.github/skills/bump-and-release into .gemini/skills/bump-and-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-and-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 Azure/autorest.python bump-and-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 Azure/autorest.python --skill bump-and-release -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/Azure/autorest.python.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/bump-and-release .github/skills/bump-and-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 "bump-and-release" agent skill from https://github.com/Azure/autorest.python/tree/main/.github/skills/bump-and-release into .github/skills/bump-and-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-and-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 Azure/autorest.python --skill bump-and-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 Azure/autorest.python bump-and-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/Azure/autorest.python.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/bump-and-release .opencode/skills/bump-and-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 "bump-and-release" agent skill from https://github.com/Azure/autorest.python/tree/main/.github/skills/bump-and-release into .opencode/skills/bump-and-release/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "bump-and-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: bump-and-release
GitHub stars: 101
Token cost: ~1.1k tokens
SKILL.md length: 368 words
Files: 1
Skills in repo: 1
Repo updated: May 22, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Bump dependency "@typespec/http-client-python" and release new versions for Azure/autorest.python repo.

Works in 10 steps: Prepare Branch → Get Latest Version and Update Dependencies → Update Dependencies → …
User wants to bump
SKILL.md covers Context Variables, Prerequisites and Workflow
Calls git, pnpm and npx

What it does

Bump And Release is an agent skill from Azure/autorest.python, published by the product's own GitHub organization. Bump dependency "@typespec/http-client-python" and release new versions for Azure/autorest.python repo. Use when user wants to bump, update, or upgrade the @typespec/http-client-python dependency, create a release PR, or publish new versions of autorest.python and typespec-python packages.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with Microsoft Azure, Python and npm. The repository describes itself as: Extension for AutoRest (https://github.com/Azure/autorest) that generates Python code. The licence is MIT.

When your agent uses it

User wants to bump
Upgrade the @typespec/http-client-python dependency
Create a release PR
Publish new versions of autorest.python and typespec-python packages

Example prompts

“@typespec/http-client-python”
“/bump-and-release”

Requirements

Python 3
Node.js

Workflow steps

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

Prepare Branch
Get Latest Version and Update Dependencies
Update Dependencies
Update peerDependencies
Verify devDependencies Versions for Specs
Run Version Tool
Check for Minor Version Bump
Build and Stage
Commit and Push
Create PR

What it can do on your machine

Read from SKILL.md and the folder at commit 28a5851. 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
- pnpm
- npx
- npm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use git, pnpm, npx and npm, 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

Bump And Release loads about 1.1k tokens when it runs. Until then it costs about 77 tokens; SKILL.md has 368 words of instructions outside code blocks.

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

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 Azure/autorest.python at commit 28a5851, republished under its MIT licence (© Azure). 368 words, ~1,098 tokens.

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

name: bump-and-release
description: Bump dependency "@typespec/http-client-python" and release new versions for Azure/autorest.python repo. Use when user wants to bump, update, or upgrade the @typespec/http-client-python dependency, create a release PR, or publish new versions of autorest.python and typespec-python packages.

Bump and Release

Bump the "@typespec/http-client-python" dependency and create a release PR for the Azure/autorest.python repository.

Context Variables

BASE_BRANCH: The branch to base changes on (default: "main")
CURRENT_DATE: Current date in YYYY-MM-DD format (e.g., "2025-01-01")

Prerequisites

Before starting, verify that npm-check-updates is available:

bash

npx npm-check-updates --version

If the command fails or prompts for installation, install it globally:

bash

npm install -g npm-check-updates

Workflow

Step 1: Prepare Branch

Navigate to the root folder of "Azure/autorest.python" repo.

If BASE_BRANCH is "main":

bash

git reset HEAD && git checkout . && git checkout origin/main && git pull origin main && git checkout -b publish/release-{{CURRENT_DATE}}

If BASE_BRANCH is not "main":

bash

git reset HEAD && git checkout . && git fetch origin {{BASE_BRANCH}} && git checkout {{BASE_BRANCH}}

Step 2: Get Latest Version and Update Dependencies

Get the latest VERSION of "@typespec/http-client-python" from npm:
bash
```
npm view @typespec/http-client-python version
```
Update the version of "@typespec/http-client-python" to ~{{VERSION}} in both files:
- packages/autorest.python/package.json
- packages/typespec-python/package.json

Steps 3–5: Update Dependencies (only if BASE_BRANCH is "main")

Skip Steps 3, 4, and 5 if BASE_BRANCH is not "main".

Step 3: Update Dependencies

Run npm-check-updates for packages/typespec-python/package.json:

bash

npx npm-check-updates -u --filter @typespec/*,@azure-tools/* --packageFile packages/typespec-python/package.json

Step 4: Update peerDependencies

Update peerDependencies in packages/typespec-python/package.json:

If format is ">=0.a.b <1.0.0": Update only the 0.a.b portion, keep the range format unchanged
If format is "^1.a.b": Update to the latest version

Step 5: Verify devDependencies Versions for Specs

Verify devDependencies versions for specs in packages/typespec-python/package.json:

Check @typespec/http-specs and @azure-tools/azure-http-specs
If the original version in package.json is newer than the updated value, keep the original version
Dev versions are typically in the form x.y.z-alpha.N-dev.M (e.g., 0.1.0-alpha.37-dev.3).

Example:

Original: @typespec/http-specs: 0.1.0-alpha.12-dev.5, updated by step 3 to 0.1.0-alpha.11 → keep 0.1.0-alpha.12-dev.5.
Original: @typespec/http-specs: 0.1.0-alpha.12-dev.5, updated by step 3 to 0.1.0-alpha.12 → keep 0.1.0-alpha.12 (step 3 works as expected).
Original: @azure-tools/azure-http-specs: 0.1.0-alpha.12-dev.2, updated to 0.1.0-alpha.11 → keep 0.1.0-alpha.12-dev.2.
Original: @azure-tools/azure-http-specs: 0.1.0-alpha.12-dev.2, updated to 0.1.0-alpha.12 → keep 0.1.0-alpha.12 (step 3 works as expected).

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

Step 6: Run Version Tool

Run the change version command:

bash

pnpm change version

Verify at least 4 files are changed:

packages/autorest.python/package.json
packages/autorest.python/CHANGELOG.md
packages/typespec-python/package.json
packages/typespec-python/CHANGELOG.md

Step 7: Check for Minor Version Bump

The version tool calculates the next version but may choose patch instead of minor incorrectly.

Run git diff to inspect updated CHANGELOG.md files
If any CHANGELOG.md contains "### Features", upgrade to minor version instead of patch version
Update version numbers in all 4 files:
- packages/autorest.python/package.json
- packages/autorest.python/CHANGELOG.md
- packages/typespec-python/package.json
- packages/typespec-python/CHANGELOG.md

Step 8: Build and Stage

bash

pnpm install && pnpm build && git add -u

Step 9: Commit and Push

bash

git commit -m "bump version"
git push origin HEAD

Step 10: Create PR

If no existing PR exists for the current branch, create a new pull request targeting the BASE_BRANCH.

Files

Just SKILL.md in .github/skills/bump-and-release of Azure/autorest.python.

Open the folder on GitHubat commit 28a5851

Compare with similar skills

Bump And 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.

Bump And Release compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Bump And Release this skillAzure/autorest.python	101	—	~1.1k	Automated safety check: Pass	MIT	4 mo ago
MCP Server BuildershareAI-lab/learn-claude-code	78k	5 repos	~1.2k	Automated safety check: Pass	MIT	11 days ago
OpenHarness End-to-End EvalsHKUDS/OpenHarness	16k	1 repos	~2.1k	Automated safety check: Notes	MIT	4 mo ago
Mem0 CLI Memory Commandsmem0ai/mem0	67k	—	~2k	Automated safety check: Notes	Apache-2.0	today
Version ReleaseNG-ZORRO/ng-zorro-antd	9.2k	—	~3.1k	Automated safety check: Pass	MIT	yesterday
Thesvgglincker/thesvg	2.8k	—	~1.5k	Automated safety check: Pass	MIT	today

Similar skills

MCP Server Builder
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
78k GitHub starsUsed in 5 repos~1.2k tokens
Agent WorkflowsAuto-check passed
OpenHarness End-to-End Evals
HKUDS/OpenHarness
Validates OpenHarness features by running real multi-turn agent loops with live LLM calls against an unfamiliar codebase, checking actual tool execution.
16k GitHub starsUsed in 1 repo~2.1k tokens
Testing & QAAuto-check: notes
Mem0 CLI Memory Commands
mem0ai/mem0
Adds, searches, lists, updates and deletes memories on the Mem0 platform from the terminal with the mem0 command, including a JSON mode built for agents.
67k GitHub stars~2k tokensUpdated today
Agent WorkflowsAuto-check: notes
Version Release
NG-ZORRO/ng-zorro-antd
NG-ZORRO/ng-zorro-antd repository release workflow. An agent skill from NG-ZORRO/ng-zorro-antd.
9.2k GitHub stars~3.1k tokensUpdated yesterday
DevelopmentAuto-check passed
Thesvg
glincker/thesvg
Fetch brand SVG logos and cloud architecture icons (AWS, Azure, GCP) from theSVG.
2.8k GitHub stars~1.5k tokensUpdated today
DevOps & CloudAuto-check passed
Tavily Search API Integration
andrewyng/context-hub
Guides building Tavily integrations for web search, URL extraction, site crawling and AI-assisted research in Python or JavaScript agent and RAG projects.
14k GitHub stars~1.1k tokensUpdated 4 mo ago
AI & LLM EngineeringAuto-check passed

Works with

Questions about Bump And Release

What does Bump And Release do?

Bump dependency "@typespec/http-client-python" and release new versions for Azure/autorest.python repo. python, published by the product's own GitHub organization.python repo.

When should I use Bump And Release?

Bump And Release fits situations like: user wants to bump; upgrade the @typespec/http-client-python dependency; create a release PR; publish new versions of autorest.python and typespec-python packages.

How do I install Bump And Release in Claude Code?

Run `npx skills add Azure/autorest.python --skill bump-and-release -a claude-code`. Or copy the skill folder (.github/skills/bump-and-release in Azure/autorest.python) into .claude/skills/bump-and-release in your project. Claude Code loads it when a task matches its description.

How do I install Bump And Release in Codex?

Run `npx skills add Azure/autorest.python --skill bump-and-release -a codex`. Or copy the skill folder (.github/skills/bump-and-release in Azure/autorest.python) into .agents/skills/bump-and-release in your project. Codex loads it when a task matches its description.

Can I use Bump And 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 Azure/autorest.python --skill bump-and-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/bump-and-release, .gemini/skills/bump-and-release, .github/skills/bump-and-release and .opencode/skills/bump-and-release in your project.

What does Bump And Release need to run?

Going by SKILL.md and its folder, Bump And Release needs the command-line tools its instructions call (git, pnpm, npx and npm). Our summary lists: Python 3; Node.js.

Does Bump And Release access the network?

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

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

Bump And 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 Bump And Release use?

About 1.1k tokens (SKILL.md is roughly 4.4k 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 Bump And Release?

Skills that share tags, products or a category with Bump And Release: MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), OpenHarness End-to-End Evals (HKUDS/OpenHarness, 16k stars), Mem0 CLI Memory Commands (mem0ai/mem0, 67k stars) and Version Release (NG-ZORRO/ng-zorro-antd, 9.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Bump And Release?

Azure (a GitHub organization, an official publisher) maintains it in Azure/autorest.python, which has 101 GitHub stars. The repository was last updated on May 22, 2026.

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

Install Bump And 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

Bump and Release

Context Variables

Prerequisites

Workflow

Step 1: Prepare Branch

Step 2: Get Latest Version and Update Dependencies

Steps 3–5: Update Dependencies (only if BASE_BRANCH is "main")

Step 3: Update Dependencies

Step 4: Update peerDependencies

Step 5: Verify devDependencies Versions for Specs

Step 6: Run Version Tool

Step 7: Check for Minor Version Bump

Step 8: Build and Stage

Step 9: Commit and Push

Step 10: Create PR

Files

Compare with similar skills

Similar skills

MCP Server Builder

OpenHarness End-to-End Evals

Mem0 CLI Memory Commands

Version Release

Thesvg

Tavily Search API Integration

Related

Questions about Bump And Release