upgrade

Automates step-by-step Java project upgrades with built-in Milestone tracking.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/brunoborges/gh-appmod --skill upgrade-brunoborges
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: upgrade
Source: https://github.com/brunoborges/gh-appmod/tree/main/skills/upgrade
Command: npx skills add https://github.com/brunoborges/gh-appmod --skill upgrade-brunoborges

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Upgrading Java runtimes, frameworks, and dependencies across multiple major versions is error-prone and time-consuming; this skill automates the planning and execution to reduce risk and manual effort.

Core Features & Use Cases

  • Analyze a project to detect current Java version, framework versions, and dependency versions, including build files like pom.xml and build.gradle.
  • Generate an upgrade plan covering major version jumps (8→11, 11→17, 17→21, 21→25) and identify potential breaking changes.
  • Apply changes incrementally across build configurations, dependencies, and source code, with validation after each step.
  • Validate builds and tests, and perform vulnerability checks on upgraded dependencies.
  • Use Case: Maintain a Java project through successive major versions by producing a safe upgrade path and implementing changes automatically.

Quick Start

Analyze your project to generate an upgrade plan, apply changes incrementally, and verify the build.

Frequently Asked Questions about upgrade

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I upgrade a Java project from version 11 to 17 automatically?

To upgrade Java projects from version 11 to 17, this skill analyzes your pom.xml or build.gradle configurations, generates an incremental upgrade plan outlining breaking changes, and applies source code modifications while validating builds and tests after each step.

What is the best way to plan a major Java version upgrade across multiple dependencies?

The best way to plan a major Java version upgrade is to analyze your current build files and dependency versions to generate a structured upgrade path, which outlines breaking changes and applies incremental modifications to ensure build validation.

Can I upgrade Maven and Gradle build configurations incrementally without breaking tests?

Yes, you can upgrade Maven and Gradle build configurations incrementally. The skill applies changes step-by-step across build files and source code, validating the build and running tests after each modification to prevent breaking your project.

Does upgrading Java dependencies automatically check for security vulnerabilities?

Upgrading Java dependencies includes vulnerability checks. After applying incremental changes to your build files and source code, the skill reports any known security vulnerabilities present in the newly upgraded dependency versions.

What are the limitations of automating a Java LTS upgrade from 8 to 25?

Automating a Java upgrade from 8 to 25 covers major version jumps including 8 to 11, 11 to 17, 17 to 21, and 21 to 25, but requires incremental validation after each step to manage breaking changes and ensure tests pass throughout the process.

When do I need to generate an upgrade plan for Java framework versions?

You need an upgrade plan for Java framework versions when moving across major Java runtime versions. The skill detects current versions in your build configurations to identify upgrade needs, present options, and outline potential breaking changes before execution.