Bump Java Version Skill
vasiliy-mikhailov/bump-java-version-skill
Upgrade automático de projetos Maven entre versões LTS Java com testes garantidos
Ver no GitHubSkill portátil que atualiza projetos Maven um passo de LTS Java por vez (8→11, 11→17, 17→21, 21→25), garantindo compilação sob a nova JDK e conservação de todos os testes que passavam antes. Usa apenas ferramentas padrão (JDKs, Maven e receitas OpenRewrite), sem scripts customizados.
Instalação
npx convez-ai vasiliy-mikhailov/bump-java-version-skill1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.
Métricas
Casos de uso
- Atualizar Maven projects entre versões Java LTS mantendo compatibilidade de testes
- Migrar de Java 8/11/17 para versões mais recentes com Spring Boot 2→3 quando necessário
- Automatizar bumps de Java com conversão javax→jakarta em projetos legados
Veredito

Skill prática e bem fundamentada para automação de migrações Java em projetos Maven. Abordagem conservadora (teste a teste) é valiosa, mas depende de dois JDKs instalados e acesso a Maven Central; ideal para times que gerenciam múltiplos projetos legados.
README
A tradução para o português deste README ainda está na fila.
bump-java-version
An Agent Skill that upgrades a Maven project one Java LTS step (8→11, 11→17, 17→21, 21→25) so it compiles under the new JDK and every test that passed before still passes — using only standard tools (JDKs, Maven, and OpenRewrite recipes from Maven Central). No project-specific scripts: the skill is a hand manual your coding agent reads and follows.
What it does
Point a tool-using coding agent at the skill and tell it the repo and the hop. It will:
- Record the baseline test set under the old JDK (the contract to conserve).
- Make Lombok safe (≥ 1.18.30).
- Run the official OpenRewrite migrate-to-Java-N recipes.
- Apply the deterministic JDK-removal fixes as plain pom edits (re-added EE deps, surefire/Mockito floors,
--add-opens, jacoco). - Compile + test under the new JDK and conserve every previously-passing test.
- Do the Spring Boot 2→3 /
javax→jakartaupgrade when a Java bump forces it. - Fall back to a troubleshooting table, or bail honestly with a reason.
Done (PASS) = mvn compile succeeds under the target JDK and no previously-passing test is lost.
Install
Claude Code
Claude Code — install it as a plugin from this repo's marketplace:
/plugin marketplace add vasiliy-mikhailov/bump-java-version-skill
/plugin install bump-java-version
It then triggers automatically when you ask Claude to upgrade or bump a Maven project's Java version.
opencode
opencode reads AGENTS.md and supports skills plugins such as opencode-skillful. Drop the skill in and reference it:
cp skills/bump-java-version/SKILL.md <your-project>/.bump-skill/SKILL.md
echo "Use .bump-skill/SKILL.md to bump this project's Java version." >> <your-project>/AGENTS.md
OpenHands
OpenHands loads skills from .openhands/skills/, and from the public extensions registry (listing in review):
mkdir -p <your-project>/.openhands/skills/bump-java-version
cp skills/bump-java-version/SKILL.md <your-project>/.openhands/skills/bump-java-version/
Kilo Code
Kilo Code installs skills from the Kilo Marketplace Skills tab (listing in review), or drop it in directly:
cp skills/bump-java-version/SKILL.md <your-project>/.bump-skill/SKILL.md
Any other agent (Cursor, Codex, Gemini CLI, …)
The skill is a single portable SKILL.md (markdown + YAML frontmatter, Agent Skills spec). Copy it where your agent reads skills, or reference it from your AGENTS.md, then prompt:
Bump this Maven project from Java
<from>to Java<to>by following.bump-skill/SKILL.md. Read it first, then carry out its steps yourself.
Requirements
- The two JDKs for the hop (e.g. JDK 17 and 21 for a 17→21 bump), selectable via
JAVA_HOME. - Maven (
mvnor the project's./mvnw). - Network access to Maven Central (for the OpenRewrite recipes and any new dependencies).
Why it's reliable
This skill wasn't hand-written. It was evolved by an AI agent across many iterations against a corpus of real GitHub repositories, and hardened on a two-rung ladder: a strong rung (Claude + Opus) first, then a production panel of three unrelated off-the-shelf agents — opencode, kilocode, and OpenHands — all driving the same model on the identical skill, the agent being the only variable. A change is kept only if it doesn't regress the corpus. Latest panel: 96 % test-conserving PASS across the three agents.