Agent skill

Skyvern Version Bump

by Skyvern-AI in 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.

AGPL-3.0Auto-check: notesDevelopment

Install Skyvern Version Bump

skills CLI
$ npx skills add Skyvern-AI/skyvern --skill bump-version -a claude-code

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

GitHub CLI
$ gh skill install Skyvern-AI/skyvern bump-version --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/Skyvern-AI/skyvern.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/bump-version .claude/skills/bump-version && 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/

Facts

Skill name
bump-version
GitHub stars
23k
Token cost
~1k tokens
SKILL.md length
401 words
Files
1
Skills in repo
6
Repo updated
First seen
Licence
AGPL-3.0

At a glance

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.

  • Works in 9 steps: Get and validate version → Create feature branch → Update pyproject.toml → …
  • Releasing a new Skyvern OSS version
  • SKILL.md covers What this does, Version argument, Step-by-step process and Important notes, plus 1 more section
  • Calls git, bash and gh; reaches claude.com; needs SKYVERN_API_KEY

What it does

The agent takes a MAJOR.MINOR.PATCH version from the argument or asks you for one, checks the format, shows the current version from `pyproject.toml` and asks you to confirm before creating a `bump-version-` branch and editing the version line. Patch, minor and major bumps are explained with short semver guidance.

It then runs the repository's two Fern scripts to build the Python SDK and the TypeScript SDK, confirms that `skyvern-ts/client/package.json` carries the new version, shows `git status` and a diff summary, and commits everything. After that it offers to run the Python SDK tests with pytest (the TypeScript tests need a manual Chrome setup) and asks again before pushing the branch and opening the pull request. If tests fail, it stops before the push.

When your agent uses it

  • Releasing a new Skyvern OSS version
  • Regenerating both Fern SDKs after changing the package version
  • Opening a version-bump pull request from a clean branch

Example prompts

  • “Bump the version to 1.0.14 and prepare the release PR.”
  • “We need a minor release. Walk me through bumping Skyvern and rebuilding the SDKs.”
  • “Bump the version, but skip the SDK tests and ask me before pushing.”

Requirements

  • A checkout of the Skyvern repository
  • Fern, which the SDK build scripts call
  • Git access to push a branch

Workflow steps

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

  1. Get and validate version
  2. Create feature branch
  3. Update pyproject.toml
  4. Build Python SDK
  5. Build TypeScript SDK
  6. Review changes
  7. Commit changes
  8. Verify SDKs (optional)
  9. Push and create PR

What it can do on your machine

Read from SKILL.md and the folder at commit f5f3f28. 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
    • bash
    • gh
    • pytest

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • claude.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names these keys or tokens, usually read from environment variables:

    • SKYVERN_API_KEY

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Skyvern Version Bump loads about 1k tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 401 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~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: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NoteMentions a .env fileSKILL.md:155
    - **Testing**: SDK tests require `.env` with `SKYVERN_API_KEY`

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 Skyvern-AI/skyvern at commit f5f3f28, republished under its AGPL-3.0 licence (© Skyvern-AI). 401 words, ~1,045 tokens.

Download SKILL.mdSave it as .claude/skills/bump-version/SKILL.md (or your agent's skills folder).
name
bump-version
description
Bump Skyvern OSS version, build Python and TypeScript SDKs with Fern, and create release PR. Use when releasing a new version or when the user asks to bump version.
argument-hint
version
disable-model-invocation
true

Bump Version Skill

Automate the complete OSS version bump and release workflow for Skyvern.

What this does

  1. Validates and updates version in pyproject.toml
  2. Builds Python SDK with Fern
  3. Builds TypeScript SDK with Fern
  4. Creates commit with all changes
  5. Optionally runs SDK tests
  6. Pushes branch and creates PR

Version argument

The version can be provided as an argument or you'll be prompted:

  • If $ARGUMENTS is provided, use it as the new version
  • If not provided, ask user for the new version number
  • Validate it follows semver format: MAJOR.MINOR.PATCH (e.g., 1.0.14, 1.1.0, 2.0.0)

Semver guidance:

  • PATCH: Bug fixes, backwards compatible (e.g., 1.0.13 → 1.0.14)
  • MINOR: New features, backwards compatible (e.g., 1.0.13 → 1.1.0)
  • MAJOR: Breaking changes (e.g., 1.0.13 → 2.0.0)

Step-by-step process

1. Get and validate version
  • Read current version from pyproject.toml line 3
  • Determine new version from $ARGUMENTS or prompt user
  • Validate semver format using regex: ^\d+\.\d+\.\d+$
  • Confirm with user: "Bumping version from {current} to {new}. Continue?"
2. Create feature branch
bash
git checkout -b bump-version-$ARGUMENTS

Branch naming: bump-version-{version} (e.g., bump-version-1.0.14)

3. Update pyproject.toml

Update line 3 in pyproject.toml:

toml
version = "{new_version}"

Use the Edit tool to make this single-line change.

4. Build Python SDK
bash
bash scripts/fern_build_python_sdk.sh
  • Wait for completion
  • Check output for errors
  • Fern reads version from pyproject.toml
5. Build TypeScript SDK
bash
bash scripts/fern_build_ts_sdk.sh
  • Wait for completion
  • Check output for errors
  • Verify skyvern-ts/client/package.json version matches new version
6. Review changes
bash
git status
git diff --stat

Show user:

  • Number of files changed
  • Which files were modified
  • Summary of changes
7. Commit changes
bash
git add .
git commit -m "Bump version to {version}

- Update version in pyproject.toml
- Regenerate Python SDK with Fern
- Regenerate TypeScript SDK with Fern

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>"
Show full SKILL.md (164 more words)Show less
8. Verify SDKs (optional)

Ask user: "Would you like to run SDK tests to verify nothing broke?"

If yes:

  • Python SDK tests: pytest tests/sdk/python_sdk/
  • Note that TypeScript tests require manual Chrome setup (see tests/sdk/README.md)
  • Display test results
  • If tests fail, STOP and report errors - do not proceed to push

If no:

  • Skip to push step
9. Push and create PR

Ask user: "Ready to push and create PR?"

If yes:

bash
git push -u origin bump-version-{version}

gh pr create --title "Bump version to {version}" --body "## Summary
Bump Skyvern OSS version to {version}

## Changes
- Updated version in \`pyproject.toml\`
- Regenerated Python SDK with Fern
- Regenerated TypeScript SDK with Fern

## Deployment
After merge, GitHub will automatically:
- Deploy Python package to PyPI (version change in \`pyproject.toml\`)
- Deploy TypeScript package to NPM (version change in \`package.json\`)

## Testing
- [ ] Python SDK tests passed locally
- [ ] TypeScript SDK tests passed locally (if applicable)

🤖 Generated with [Claude Code](https://claude.com/claude-code)"

Display the PR URL to the user.

Important notes

  • Single PR: All changes (version bump, SDK generation, commit) happen in one PR
  • Fern sync: Fern reads version from pyproject.toml and syncs to package.json
  • Testing: SDK tests require .env with SKYVERN_API_KEY
  • Deployment: Automatic on PR merge via GitHub Actions
  • No force push: Never use --force when pushing

Error handling

If any step fails:

  1. Display the error message clearly
  2. Explain what went wrong
  3. Ask user how to proceed (fix, skip, or abort)
  4. Do not continue to next steps if critical operations fail

© Skyvern-AI, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/bump-version of Skyvern-AI/skyvern.

Open the folder on GitHubat commit f5f3f28

Compare with similar skills

Skyvern Version Bump 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.

Skyvern Version Bump compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Skyvern Version Bump this skillSkyvern-AI/skyvern23k—~1kAutomated safety check: NotesAGPL-3.0
pybind11 Release Preparationpybind/pybind1118k—~1.7kAutomated safety check: PassCustom licence
Adk Gitgoogle/adk-python22k—~1.3kAutomated safety check: PassApache-2.0
Adk Setupgoogle/adk-python22k—~993Automated safety check: NotesApache-2.0
GitHub Fork and PR Submissionjxxghp/MoviePilot12k—~1.1kAutomated safety check: NotesGPL-3.0
Markbind Typescript MigrationMarkBind/markbind158—~2kAutomated safety check: PassMIT

Similar skills

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

    18k GitHub stars~1.7k tokensUpdated today
    DevelopmentAuto-check passed
  • Adk Git

    google/adk-python

    Official

    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…

    22k GitHub stars~1.3k tokensUpdated today
    DevelopmentAuto-check passed
  • Adk Setup

    google/adk-python

    Official

    Sets up a local ADK Python development environment in a git clone of the open-source adk-python repository: a uv virtual environment, all dependency extras, pre-commit hooks, and a first unit-test…

    22k GitHub stars~993 tokensUpdated today
    DevelopmentAuto-check: notes
  • 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.

    12k GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check: notes
  • Complete guide for migrating JavaScript files to TypeScript in the MarkBind project, including the two-commit strategy, import/export syntax conversion, and best practices.

    158 GitHub stars~2k tokensUpdated 1 mo ago
    DevelopmentAuto-check passed
  • GitHub PR Description

    lucasvieirasilva/nx-plugins

    Generates a GitHub Pull Request description for this repository from the commits on the current branch, filling in .github/PULLREQUESTTEMPLATE.md (Current Behavior / Expected Behavior / Related…

    153 GitHub stars~1.4k tokensUpdated 11 days ago
    DevelopmentAuto-check passed

More from Skyvern-AI/skyvern

  • Skyvern Browser Automation

    Skyvern-AI/skyvern

    Picks the right Skyvern CLI command for a web task, from quick yes/no checks to reusable multi-page workflows, instead of falling back to plain page fetching.

    23k GitHub starsUsed in 1 repo~2.9k tokens
    Auto-check passed
  • Skyvern Browser Automation

    Skyvern-AI/skyvern

    Automates websites with Skyvern's AI browser agent to fill forms, extract data, download files, log in and run multi-step workflows through SDKs, REST, MCP or a CLI.

    23k GitHub stars~1.9k tokensUpdated today
    Auto-check passed
  • Smoke-tests a Skyvern deployment by checking the backend API, frontend rendering, browser session provisioning and workflow execution in sequence.

    23k GitHub stars~1.5k tokensUpdated today
    Auto-check passed
  • Diff-Driven Smoke Tests

    Skyvern-AI/skyvern

    Reads your git diff, writes a handful of happy-path browser smoke tests, runs them with Skyvern or Chrome DevTools MCP and posts screenshot evidence to the PR.

    23k GitHub stars~5.2k tokensUpdated today
    Auto-check passed
  • Diff-Driven QA

    Skyvern-AI/skyvern

    Reads your git diff, decides whether the change needs browser QA, API checks or repo tests, runs that validation and reports pass or fail with evidence.

    23k GitHub stars~4.7k tokensUpdated today
    Auto-check: warnings

Categories

Questions about Skyvern Version Bump

What does Skyvern Version Bump do?

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. toml` and asks you to confirm before creating a `bump-version-` branch and editing the version line. Patch, minor and major bumps are explained with short semver guidance.

When should I use Skyvern Version Bump?

Skyvern Version Bump fits situations like: releasing a new Skyvern OSS version; regenerating both Fern SDKs after changing the package version; opening a version-bump pull request from a clean branch.

How do I install Skyvern Version Bump in Claude Code?

Run `npx skills add Skyvern-AI/skyvern --skill bump-version -a claude-code`. Or copy the skill folder (.claude/skills/bump-version in Skyvern-AI/skyvern) into .claude/skills/bump-version in your project. Claude Code loads it when a task matches its description.

How do I install Skyvern Version Bump in Codex?

Run `npx skills add Skyvern-AI/skyvern --skill bump-version -a codex`. Or copy the skill folder (.claude/skills/bump-version in Skyvern-AI/skyvern) into .agents/skills/bump-version in your project. Codex loads it when a task matches its description.

Can I use Skyvern Version Bump 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 Skyvern-AI/skyvern --skill bump-version -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-version, .gemini/skills/bump-version, .github/skills/bump-version and .opencode/skills/bump-version in your project.

What does Skyvern Version Bump need to run?

Going by SKILL.md and its folder, Skyvern Version Bump needs the command-line tools its instructions call (git, bash, gh and pytest) and credentials named SKYVERN_API_KEY. Our summary lists: A checkout of the Skyvern repository; Fern, which the SDK build scripts call; Git access to push a branch.

Does Skyvern Version Bump access the network?

SKILL.md names 1 domain. In commands or code: claude.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Skyvern Version Bump safe to install?

Our automated static check of SKILL.md found notes only (mentions a .env file), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Skyvern Version Bump use?

Skyvern Version Bump is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Skyvern Version Bump use?

About 1k tokens (SKILL.md is roughly 4.2k 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 Skyvern Version Bump?

Skills that share tags, products or a category with Skyvern Version Bump: pybind11 Release Preparation (pybind/pybind11, 18k stars), Adk Git (google/adk-python, 22k stars), Adk Setup (google/adk-python, 22k stars) and GitHub Fork and PR Submission (jxxghp/MoviePilot, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Skyvern Version Bump?

Skyvern-AI (a GitHub organization) maintains it in Skyvern-AI/skyvern, which has 23,172 GitHub stars. The repository holds 6 skills in this directory. The repository was last updated on October 10, 2026.

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