Agent skill

Batch Deps Upgrade

Batch all open Dependabot dependency upgrade PRs into a single PR

ISCAuto-check passedDevelopment

Install Batch Deps Upgrade

skills CLI

$ npx skills add XRPLF/xrpl4j --skill batch-deps-upgrade -a claude-code

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

GitHub CLI

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

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 XRPLF/xrpl4j --skill batch-deps-upgrade -a codex

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

GitHub CLI

$ gh skill install XRPLF/xrpl4j batch-deps-upgrade --agent codex

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

Manual copy

$ git clone --depth 1 https://github.com/XRPLF/xrpl4j.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/batch-deps-upgrade .agents/skills/batch-deps-upgrade && 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 "batch-deps-upgrade" agent skill from https://github.com/XRPLF/xrpl4j/tree/main/.claude/skills/batch-deps-upgrade into .agents/skills/batch-deps-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "batch-deps-upgrade", 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 XRPLF/xrpl4j --skill batch-deps-upgrade -a cursor

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

GitHub CLI

$ gh skill install XRPLF/xrpl4j batch-deps-upgrade --agent cursor

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

Manual copy

$ git clone --depth 1 https://github.com/XRPLF/xrpl4j.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/batch-deps-upgrade .cursor/skills/batch-deps-upgrade && 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 "batch-deps-upgrade" agent skill from https://github.com/XRPLF/xrpl4j/tree/main/.claude/skills/batch-deps-upgrade into .cursor/skills/batch-deps-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "batch-deps-upgrade", 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/XRPLF/xrpl4j.git --path .claude/skills/batch-deps-upgrade

--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 XRPLF/xrpl4j --skill batch-deps-upgrade -a gemini-cli

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

GitHub CLI

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

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 XRPLF/xrpl4j --skill batch-deps-upgrade -a github-copilot

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

Manual copy

$ git clone --depth 1 https://github.com/XRPLF/xrpl4j.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/batch-deps-upgrade .github/skills/batch-deps-upgrade && 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 "batch-deps-upgrade" agent skill from https://github.com/XRPLF/xrpl4j/tree/main/.claude/skills/batch-deps-upgrade into .github/skills/batch-deps-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "batch-deps-upgrade", 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 XRPLF/xrpl4j --skill batch-deps-upgrade -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 XRPLF/xrpl4j batch-deps-upgrade --agent opencode

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

Manual copy

$ git clone --depth 1 https://github.com/XRPLF/xrpl4j.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/batch-deps-upgrade .opencode/skills/batch-deps-upgrade && 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 "batch-deps-upgrade" agent skill from https://github.com/XRPLF/xrpl4j/tree/main/.claude/skills/batch-deps-upgrade into .opencode/skills/batch-deps-upgrade/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "batch-deps-upgrade", 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: batch-deps-upgrade
GitHub stars: 133
Token cost: ~1.6k tokens
SKILL.md length: 828 words
Files: 2
Skills in repo: 1
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: ISC

At a glance

Batch all open Dependabot dependency upgrade PRs into a single PR

Works in 4 steps: Discover → Apply → Validate → …
Tasks that involve Dependency management
SKILL.md covers Step 1: Discover, Step 2: Apply, Step 3: Validate and Step 4: Generate Outputs
Calls mvn and gh

What it does

Batch Deps Upgrade is an agent skill from XRPLF/xrpl4j. Batch all open Dependabot dependency upgrade PRs into a single PR

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `README.md`).

It sits in Development, covering Dependency management. It works with Java. The repository describes itself as: A 100% Java implementation to interact with the XRP Ledger. The licence is ISC.

When your agent uses it

Tasks that involve Dependency management

Example prompts

“/batch-deps-upgrade”

Workflow steps

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

Discover
Apply
Validate
Generate Outputs

What it can do on your machine

Read from SKILL.md and the folder at commit 30002cd. 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:
- mvn
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, 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

Batch Deps Upgrade loads about 1.6k tokens when it runs. Until then it costs about 21 tokens; SKILL.md has 828 words of instructions outside code blocks.

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

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 XRPLF/xrpl4j at commit 30002cd, republished under its ISC licence (© XRPLF). 828 words, ~1,592 tokens.

Download SKILL.mdSave it as .claude/skills/batch-deps-upgrade/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: batch-deps-upgrade
description: Batch all open Dependabot dependency upgrade PRs into a single PR
disable-model-invocation: true

Batch all open Dependabot dependency upgrade PRs into a single PR for this repository.

Step 1: Discover

Run: gh pr list --repo XRPLF/xrpl4j --label dependencies --state open --limit 500 --json number,title,headRefName,body,url

Parse each PR to extract coordinates and versions. Maven Dependabot PRs come in two formats:

Single-package PRs: title is Bump <groupId>:<artifactId> from <old> to <new> — parse groupId, artifactId, old version, and new version from title
Property PRs: title is Bump <propertyName> from <old> to <new> — the property name maps to a <properties> entry in pom.xml (e.g., jackson.version, feign.version)
Grouped PRs: title lists multiple packages — parse from PR body, which contains a structured list of package updates

If any PR can't be parsed from either title or body, flag it for manual review. Build a table of all proposed upgrades. Report the table to the user before proceeding.

Also note: Dependabot sometimes opens duplicate PRs for the same dependency across submodules (e.g., xrpl4j-core/org.assertj-assertj-core-3.27.7 and xrpl4j-integration-tests/org.assertj-assertj-core-3.27.7). Deduplicate — if the version is managed centrally in the root pom.xml <dependencyManagement> or <properties>, one update covers all submodules. Mark the duplicates as No-op (managed by root pom).

Step 2: Apply

If a target branch already exists for this quarter's upgrades, work on that branch. Otherwise create a new branch from main: deps/batch-deps-upgrade-YYYY-QN (use current year and quarter).
Inspect the root pom.xml to determine where each dependency's version is controlled:
- Version property: a <properties> entry like <jackson.version>2.14.0</jackson.version> — update the property value
- Direct version in <dependencyManagement>: a <version> element — update it directly
- BOM import in <dependencyManagement>: a <dependency> with <type>pom</type><scope>import</scope> — update its <version>
- Maven plugin version: in <build><pluginManagement><plugins> — update the <version> element
Check for compatibility constraints before upgrading:
- Java version: read maven.compiler.source from pom.xml. If a dependency's new version requires a higher Java version than the project's compiler source, mark it as Skipped immediately — do not attempt the upgrade. Known constraints: caffeine 3.x requires Java 11+, junit-bom 6.x requires Java 17+.
- API changes: major version bumps may require source-level changes (e.g., changed APIs, removed methods, renamed classes). Flag these as needing extra validation.
Apply each upgrade by editing pom.xml directly. For version properties, use mvn versions:set-property -Dproperty=<name> -DnewVersion=<version> -DprocessAllModules as an alternative to manual XML edits — but verify the result looks correct before proceeding.
Run mvn dependency:resolve -q to verify the dependency graph resolves without conflicts after applying all changes.
Classify each Dependabot PR as:
- Upgraded: version changed in pom.xml
- No-op: version was already current or newer, or is a duplicate submodule PR covered by a root-pom change
- Skipped: compatibility issue or unresolvable conflict

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

Step 3: Validate

Run the build and test suite in order:

mvn clean install
- This compiles all modules, runs checkstyle, runs unit tests, and runs integration tests
If step 1 fails, attempt to fix the breaking change with code modifications before rolling back. Common patterns for Java/Maven:
- Removed or renamed API (e.g., a method removed in a major version): update call sites to use the new API
- Changed constructor or builder pattern: adapt usage to the new API
- Checkstyle violations from new code patterns: fix the style issue
- Compile errors from changed generics or type parameters: adjust the type annotations
- Breaking changes in BouncyCastle (crypto library): the API often changes significantly between major versions — check migration notes
- JUnit 5 → 6 migration: junit-bom 6.x requires Java 17+ (class file version 61.0) — skip unless the project has already raised its minimum Java version to 17
Only roll back and mark as Skipped if:
- The fix requires a large-scale migration across many files
- The upgrade is blocked by an incompatible transitive dependency you cannot resolve
If a failure persists after investigation, roll back the upgrade and mark it as Skipped. Re-run validation until green.

Step 4: Generate Outputs

Do NOT commit or create a PR. Instead, generate the following outputs for the human to use:

Code changes note — write a markdown file (.claude/skills/batch-deps-upgrade/code-changes.md) documenting every non-pom.xml source code change: what broke, why, and the minimal fix applied.
Commit message — output a concise commit message the human can copy-paste. Format: chore(deps): quarterly batch dependency upgrade YYYY-QN followed by a brief summary of upgrades, skips, and no-ops.
PR description — write a markdown file (.claude/skills/batch-deps-upgrade/pr-description.md) containing:
- A summary section describing the batch upgrade
- A "Superseded Dependabot PRs" table with columns: PR (linked), Package (groupId:artifactId), From, To, Status, MajorVersionUpgrade
  - Status values: Upgraded, No-op (reason), Skipped (reason: compatibility issue / build failure: error)
  - MajorVersionUpgrade: No if the major version number did not change. Otherwise Yes plus a link for each major version crossed — link to the package's Maven Central release notes, GitHub releases page, or CHANGELOG.md. Verify each link returns HTTP 200 before including it.
- Closing instructions with two paragraphs:
  1. "After merging, close the following superseded PRs (Skipped ones remain open for future handling): #X, #Y, #Z" — list only Upgraded and No-op PRs.
  2. "The following PRs were Skipped and should remain open: #A (groupId:artifactId), #B (groupId:artifactId), ..." — these stay open so Dependabot keeps rebasing them.

Files

SKILL.md and 1 other file in .claude/skills/batch-deps-upgrade of XRPLF/xrpl4j.

SKILL.md
README.md

Open the folder on GitHubat commit 30002cd

Compare with similar skills

Batch Deps Upgrade 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.

Batch Deps Upgrade compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Batch Deps Upgrade this skillXRPLF/xrpl4j	133	—	~1.6k	Automated safety check: Pass	ISC	2 days ago
WxJava Upgrade Guidebinarywang/WxJava	33k	—	~129	Automated safety check: Pass	Apache-2.0	today
Dependabot PR Reviewkernitus/BukkitOldCombatMechanics	225	—	~882	Automated safety check: Pass	MPL-2.0	5 days ago
Maven Dependency ManagementTheBushidoCollective/han	198	1 repos	~3.1k	Automated safety check: Notes	Custom licence	1 mo ago
Grails 8 Upgrade Guideapache/grails-core	2.9k	—	~20k	Automated safety check: Pass	Apache-2.0	today
110 Java Maven Best Practicesjabrena/plinth	447	—	~1.4k	Automated safety check: Pass	Apache-2.0	2 days ago

Similar skills

WxJava Upgrade Guide
binarywang/WxJava
Plans a WxJava version upgrade, checking the BOM, module dependencies, JDK version and configuration, with phased steps and clear rollback conditions.
33k GitHub stars~129 tokensUpdated today
DevelopmentAuto-check passed
Dependabot PR Review
kernitus/BukkitOldCombatMechanics
A skill your agent uses for Dependabot PRs, dependency bumps, Gradle or Maven dependency updates, GitHub Actions updates, dependency changelog/licence/release-note review, JVM/classfile checks, and…
225 GitHub stars~882 tokensUpdated 5 days ago
DevelopmentAuto-check passed
Maven Dependency Management
TheBushidoCollective/han
A skill your agent uses when managing Maven dependencies, resolving dependency conflicts, configuring BOMs, or optimizing dependency trees in Java projects.
198 GitHub starsUsed in 1 repo~3.1k tokens
DevelopmentAuto-check: notes
Grails 8 Upgrade Guide
apache/grails-core
Guides moving a Grails application from 7.x to Grails 8 and turns the official upgrade guide into a checklist of breaking changes.
2.9k GitHub stars~20k tokensUpdated today
DevelopmentAuto-check passed
110 Java Maven Best Practices
jabrena/plinth
A skill your agent uses when you need to review, improve, or troubleshoot a Maven pom.xml file — including dependency management with BOMs, plugin configuration, version centralization, multi-module…
447 GitHub stars~1.4k tokensUpdated 2 days ago
DevelopmentAuto-check passed
Senior Java
benchflow-ai/skillsbench
World-class Java and Spring Boot development skill for enterprise applications, microservices, and cloud-native systems.
1.8k GitHub stars~5k tokensUpdated 2 mo ago
Backend & APIsAuto-check passed

Works with

Java

Questions about Batch Deps Upgrade

What does Batch Deps Upgrade do?

Batch all open Dependabot dependency upgrade PRs into a single PR. Batch Deps Upgrade is an agent skill from XRPLF/xrpl4j.

When should I use Batch Deps Upgrade?

Batch Deps Upgrade fits situations like: tasks that involve Dependency management.

How do I install Batch Deps Upgrade in Claude Code?

Run `npx skills add XRPLF/xrpl4j --skill batch-deps-upgrade -a claude-code`. Or copy the skill folder (.claude/skills/batch-deps-upgrade in XRPLF/xrpl4j) into .claude/skills/batch-deps-upgrade in your project. Claude Code loads it when a task matches its description.

How do I install Batch Deps Upgrade in Codex?

Run `npx skills add XRPLF/xrpl4j --skill batch-deps-upgrade -a codex`. Or copy the skill folder (.claude/skills/batch-deps-upgrade in XRPLF/xrpl4j) into .agents/skills/batch-deps-upgrade in your project. Codex loads it when a task matches its description.

Can I use Batch Deps Upgrade 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 XRPLF/xrpl4j --skill batch-deps-upgrade -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/batch-deps-upgrade, .gemini/skills/batch-deps-upgrade, .github/skills/batch-deps-upgrade and .opencode/skills/batch-deps-upgrade in your project.

What does Batch Deps Upgrade need to run?

Going by SKILL.md and its folder, Batch Deps Upgrade needs the command-line tools its instructions call (mvn and gh).

Does Batch Deps Upgrade access the network?

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

Is Batch Deps Upgrade 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 Batch Deps Upgrade use?

Batch Deps Upgrade is published under the ISC licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Batch Deps Upgrade use?

About 1.6k tokens (SKILL.md is roughly 6.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 Batch Deps Upgrade?

Skills that share tags, products or a category with Batch Deps Upgrade: WxJava Upgrade Guide (binarywang/WxJava, 33k stars), Dependabot PR Review (kernitus/BukkitOldCombatMechanics, 225 stars), Maven Dependency Management (TheBushidoCollective/han, 198 stars) and Grails 8 Upgrade Guide (apache/grails-core, 2.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Batch Deps Upgrade?

XRPLF (a GitHub organization) maintains it in XRPLF/xrpl4j, which has 133 GitHub stars. The repository was last updated on October 7, 2026.

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

Install Batch Deps Upgrade

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Step 1: Discover

Step 2: Apply

Step 3: Validate

Step 4: Generate Outputs

Files

Compare with similar skills

Similar skills

WxJava Upgrade Guide

Dependabot PR Review

Maven Dependency Management

Grails 8 Upgrade Guide

110 Java Maven Best Practices

Senior Java

Related

Questions about Batch Deps Upgrade