New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Fory Version Bump

by apache in apache/fory

Bump Apache Fory release or post-release development versions across Java, Kotlin, Scala, Python, Rust, Go, C++, C, Dart, JavaScript, Swift, integration tests, examples, and source docs.

Apache-2.0Auto-check passedMobile

Install Fory Version Bump

skills CLI
$ npx skills add apache/fory --skill fory-version-bump -a claude-code

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

GitHub CLI
$ gh skill install apache/fory fory-version-bump --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/apache/fory.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/fory-version-bump .claude/skills/fory-version-bump && 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
fory-version-bump
GitHub stars
4.6k
Token cost
~1.1k tokens
SKILL.md length
338 words
Files
2
Skills in repo
3
Repo updated
First seen
Licence
Apache-2.0

At a glance

Bump Apache Fory release or post-release development versions across Java, Kotlin, Scala, Python, Rust, Go, C++, C, Dart, JavaScript, Swift, integration tests, examples, and source docs.

  • Works in 4 steps: Read AGENTS.md, tasks/lessons.md,… → Record the released and next-development… → For a post-release bump, run → …
  • Preparing a release version
  • SKILL.md covers Version Intent, Ecosystem Version Forms, Workflow and Verification Boundary, plus 1 more section
  • Calls git, rg and python

What it does

Fory Version Bump is an agent skill from apache/fory. Bump Apache Fory release or post-release development versions across Java, Kotlin, Scala, Python, Rust, Go, C++, C, Dart, JavaScript, Swift, integration tests, examples, and source docs. Use when preparing a release version, moving main to the next development version, switching install docs to a released version, or auditing Fory version consistency after release scripts run.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Mobile, covering Integration testing, Android development and iOS development. It works with JavaScript, Rust, C++ and Java. The repository describes itself as: A blazingly fast multi-language serialization framework for idiomatic domain objects, schema IDL, and cross-language data exchange. The licence is Apache-2.0.

When your agent uses it

  • Preparing a release version
  • Moving main to the next development version
  • Switching install docs to a released version
  • Auditing Fory version consistency after release scripts run

Example prompts

  • “/fory-version-bump”

Requirements

  • Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Read AGENTS.md, tasks/lessons.md, .agents/docs-and-formatting.md, and
  2. Record the released and next-development versions in the task file.
  3. For a post-release bump, run
  4. Inspect the complete diff. The helper should update package/build metadata,

What it can do on your machine

Read from SKILL.md and the folder at commit dcf8d24. 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
    • rg
    • python
    • prettier

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

  • Network

    No URLs in SKILL.md. Its commands use git, 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

Fory Version Bump loads about 1.1k tokens when it runs. Until then it costs about 100 tokens; SKILL.md has 338 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~100
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 apache/fory at commit dcf8d24, republished under its Apache-2.0 licence (© apache). 338 words, ~1,084 tokens.

Download SKILL.mdSave it as .claude/skills/fory-version-bump/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
fory-version-bump
description
Bump Apache Fory release or post-release development versions across Java, Kotlin, Scala, Python, Rust, Go, C++, C#, Dart, JavaScript, Swift, integration tests, examples, and source docs. Use when preparing a release version, moving main to the next development version, switching install docs to a released version, or auditing Fory version consistency after release scripts run.

Fory Version Bump

Version Intent

Separate these two targets before editing:

  • Released version: use in install docs, examples, and package-manager snippets.
  • Next development version: use in active package and build metadata.

Do not edit fory-site unless the user explicitly includes that repository.

Ecosystem Version Forms

Let ci/release.py normalize the input instead of converting versions by hand.

For input 1.1.0-dev, expected forms are:

SurfaceExpected form
Java, Kotlin, Scala, Maven integration projects1.1.0-SNAPSHOT
Python and compiler packages1.1.0.dev0
Rust packages and path dependency versions1.1.0-alpha.0
Go module dependencies on Foryv1.1.0-alpha.0
JavaScript package versions1.1.0-alpha.0
Dart packages1.1.0-dev
C# package metadata1.1.0-dev
CMake project versions1.1.0
Bazel module version1.1.0
User install docs after a 1.0.0 release1.0.0

Workflow

  1. Read AGENTS.md, tasks/lessons.md, .agents/docs-and-formatting.md, and ./.local/AGENTS.md when present. Review git status --short --branch.
  2. Record the released and next-development versions in the task file.
  3. For a post-release bump, run:
bash
python ci/release.py bump_version -l all -version <next-dev-version> \
  -release-version <released-version>
  1. Inspect the complete diff. The helper should update package/build metadata, source docs, examples, and these historically missed surfaces:
  • MODULE.bazel
  • javascript/package-lock.json
  • integration_tests/idl_tests/kotlin/pom.xml
  • integration_tests/idl_tests/dart/pubspec.yaml
  • integration_tests/idl_tests/rust/Cargo.lock
  • dart/CHANGELOG.md and dart/packages/fory/CHANGELOG.md
  • scala/fory-scala/README.md and scala/fory-json-scala/README.md
  1. Search for stale previous development forms and accidental next-development versions in user-facing docs:
bash
rg -n '<previous-development-version-regex>' \
  --glob '!tasks/**' --glob '!**/target/**' --glob '!**/build/**' \
  --glob '!**/bin/**' --glob '!**/obj/**' --glob '!**/node_modules/**'
rg -n '<next-development-version-regex>' \
  README.md docs csharp/README.md swift/README.md scala/README.md \
  java/README.md rust/README.md dart/packages/fory/README.md examples \
  --glob '!**/target/**' --glob '!**/build/**' --glob '!**/node_modules/**'

Inspect every hit. Keep unrelated third-party versions, benchmark numbers, historical changelog entries, test fixtures, and ignored build outputs unchanged.

  1. Format changed Markdown and check the patch:
bash
prettier --write <changed-markdown-files>
git diff --check

Verification Boundary

Treat a version-only bump as a textual metadata and documentation update. Do not run unit tests, builds, Maven, CMake, Cargo metadata, package-manager validation, or language test suites locally, including through subagents, unless the user explicitly asks. CI owns those checks.

Verify only that:

  • each ecosystem uses the expected version form;
  • install docs use the released version and development metadata uses the next version;
  • changelogs contain the released version before the next development section;
  • no unexplained stale development version remains;
  • formatting and git diff --check pass; and
  • task files are not staged.

Finish

  • Summarize exact version forms used by ecosystem.
  • Note any intentionally retained old version hits.
  • Commit tracked code and documentation changes, excluding task scratch files.

© apache, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/fory-version-bump of apache/fory.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit dcf8d24

Compare with similar skills

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

Fory Version Bump compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Fory Version Bump this skillapache/fory4.6k—~1.1kAutomated safety check: PassApache-2.0
Build Teaql Appteaql/teaql-agent-kit2.8k—~4.6kAutomated safety check: PassMIT
Test Smell Detectiondotnet/skills5.6k1 repos~2.5kAutomated safety check: PassMIT
Grade Testsdotnet/skills5.6k1 repos~5.2kAutomated safety check: PassMIT
Dbgtheodo-group/debug-that158—~1.9kAutomated safety check: PassMIT
Supercovsupercorp-ai/supercov1481 repos~415Automated safety check: PassMIT

Similar skills

  • Build Teaql App

    teaql/teaql-agent-kit

    Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries.

    2.8k GitHub stars~4.6k tokensUpdated 10 days ago
    MobileAuto-check passed

  • Test Smell Detection

    dotnet/skills

    Official

    Audits existing tests in any language using formal, research-backed test smell names and the testsmells.org 19-smell academic taxonomy.

    5.6k GitHub starsUsed in 1 repo~2.5k tokens
    MobileAuto-check passed

  • Grade Tests

    dotnet/skills

    Official

    Assess a curated list of tests and produce a PR-ready table with a primary Pass, Failed, Uncertain, or Not applicable result plus A-F quality detail for every resolved test; Uncertain and Not…

    5.6k GitHub starsUsed in 1 repo~5.2k tokens
    MobileAuto-check passed

  • Dbg

    theodo-group/debug-that

    Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.

    158 GitHub stars~1.9k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed

  • Supercov

    supercorp-ai/supercov

    Measures test coverage and code quality in a repository with the supercov CLI, and turns what it finds into small, focused tests or fixes.

    148 GitHub starsUsed in 1 repo~415 tokens
    Testing & QAAuto-check passed

  • Code Reviewer

    alirezarezvani/claude-skills

    Code review automation for TypeScript, JavaScript, Python, Go, Swift, Kotlin, C, .NET, Java, C, C++, Rust, Ruby, PHP, and Dart/Flutter.

    28k GitHub starsUsed in 1 repo~1.6k tokens
    DevelopmentAuto-check passed

More from apache/fory

  • Fory Release

    apache/fory

    Prepare an Apache Fory release candidate from a clean release branch, including the version bump, RC tag, JVM staging, ASF source artifacts, SVN upload, and vote email.

    4.6k GitHub stars~2.9k tokensUpdated today
    Auto-check passed

  • Fory Performance Optimization

    apache/fory

    Run profile-driven bottleneck optimization across Apache Fory implementations (Java, C++, Python/Cython, Go, Rust, Swift, C, JavaScript/TypeScript, Dart, Kotlin, Scala).

    4.6k GitHub stars~2.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Fory Version Bump

What does Fory Version Bump do?

Bump Apache Fory release or post-release development versions across Java, Kotlin, Scala, Python, Rust, Go, C++, C, Dart, JavaScript, Swift, integration tests, examples, and source docs. Fory Version Bump is an agent skill from apache/fory. Bump Apache Fory release or post-release development versions across Java, Kotlin, Scala, Python, Rust, Go, C++, C, Dart, JavaScript, Swift, integration tests, examples, and source docs.

When should I use Fory Version Bump?

Fory Version Bump fits situations like: preparing a release version; moving main to the next development version; switching install docs to a released version; auditing Fory version consistency after release scripts run.

How do I install Fory Version Bump in Claude Code?

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

How do I install Fory Version Bump in Codex?

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

Can I use Fory 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 apache/fory --skill fory-version-bump -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fory-version-bump, .gemini/skills/fory-version-bump, .github/skills/fory-version-bump and .opencode/skills/fory-version-bump in your project.

What does Fory Version Bump need to run?

Going by SKILL.md and its folder, Fory Version Bump needs the command-line tools its instructions call (git, rg, python and prettier). Our summary lists: Python 3.

Does Fory Version Bump access the network?

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

Is Fory Version Bump 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 Fory Version Bump use?

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

How many tokens does Fory Version Bump use?

About 1.1k tokens (SKILL.md is roughly 4.3k 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 Fory Version Bump?

Skills that share tags, products or a category with Fory Version Bump: Build Teaql App (teaql/teaql-agent-kit, 2.8k stars), Test Smell Detection (dotnet/skills, 5.6k stars), Grade Tests (dotnet/skills, 5.6k stars) and Dbg (theodo-group/debug-that, 158 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fory Version Bump?

apache (a GitHub organization) maintains it in apache/fory, which has 4,566 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 7, 2026.

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