java-upgrade Skill
Transformation rules and verification steps for upgrading Java 8/11 + Spring Boot 2.x applications to Java 21 + Spring Boot 3.x. WHEN: upgrade Java version, migrate Spring Boot 2 to 3, javax to jakarta, fix CVE in Java dependencies, update Maven/Gradle build for Java 21, Spring Security 5 to 6 migration. NOT for: green Published by microsoft in MicroHack.
Decision snapshot
Is this a fit?
Security review, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is java-upgrade Skill?
Transformation rules and verification steps for upgrading Java 8/11 + Spring Boot 2.x applications to Java 21 + Spring Boot 3.x. WHEN: upgrade Java version, migrate Spring Boot 2 to 3, javax to jakarta, fix CVE in Java dependencies, update Maven/Gradle build for Java 21, Spring Security 5 to 6 migration. NOT for: green Published by microsoft in MicroHack. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Security review
- Security review use cases
Declared skill metadata
- Source file: 03-Azure/01-01-App Innovation/03_GHCPAppModernization/templates/skills/java-upgrade/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use java-upgrade Skill
- Use it for security review.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/MicroHack
- Skill file: 03-Azure/01-01-App Innovation/03_GHCPAppModernization/templates/skills/java-upgrade/SKILL.md
What it does
Transformation rules and verification steps for upgrading Java 8/11 + Spring Boot 2.x applications to Java 21 + Spring Boot 3.x. WHEN: upgrade Java version, migrate Spring Boot 2 to 3, javax to jakarta, fix CVE in Java dependencies, update Maven/Gradle build for Java 21, Spring Security 5 to 6 migration. NOT for: green
Skill instructions
Java 8 / Spring Boot 2.x → Java 21 / Spring Boot 3.x Upgrade Rules Purpose Packages the version-step strategy, API mappings, and verification checklist for a behavior-preserving upgrade to Java 21 + Spring Boot 3.x. Prerequisites - ASSESSMENT.md exists and is approved. - JDK 21 + compatible Maven installed — verify: java -version, mvn -version. Procedure Step 1 — Upgrade incrementally (never skip) | Step | From → To | Key risk at this step | |---|---|---| | 1 | Java 8 → 11 | Removed JEE modules (JAXB, JAX-WS) — add explicit deps | | 2 | Java 11 → 17 | Strong encapsulation of JDK internals (--add-opens smells) | | 3 | Java 17 → 21 | Mostly safe; check agents/bytecode libs (ASM, CGLIB versions) | | 4 | Boot 2.x → 2.7 | Deprecation cleanup before the big jump | | 5 | Boot 2.7 → 3.x | javax → jakarta, Spring Security 6, Hibernate 6 | powershell mvn -q clean verify run after EVERY step; fix before proceeding Step 2 — Apply transformation rules (Boot 2.7 → 3.x) | Source pattern | Target patt
Verified compatibility and discovery
Frequently asked questions
What is java-upgrade?
java-upgrade is a open-source AI agent skill with Copy skill directory. Transformation rules and verification steps for upgrading Java 8/11 + Spring Boot 2.x applications to Java 21 + Spring Boot 3.x.
Who is java-upgrade best for?
java-upgrade is best for reusing agent instructions, scripts, and references, security review workflows.
How do I install java-upgrade?
Install or run java-upgrade using Copy skill directory. Check java-upgrade for the latest setup command.
Is java-upgrade actively maintained?
java-upgrade may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
