Migrate Spring Boot 3.5 applications to Boot 4 with staged agent checks
Use the named Spring Boot migration skill to prepare a focused upgrade diff and verify dependency, configuration, JSON and startup behavior.
npx skills add agentskillexchange/skills --skill migrate-spring-boot-35-applications-to-boot-4-with-staged-agent-checks
Invoke the upstream spring-boot-migration skill when an agent must plan or implement a Spring Boot 3.5 to Boot 4 upgrade. Supply the application repository, current dependency and Java baselines, target Boot release, supported profiles, build commands, and permission to edit. The result is a staged migration plan and, when requested, a reviewable upgrade diff with verification evidence.
What this skill actually does
Start by capturing passing tests, dependency reports and JSON contracts on the latest supported Boot 3.5 baseline. Read the exact migration SKILL.md and its good-migration-plan example. Check the official target-version requirements linked by upstream before choosing dependency versions. Migrate focused main and test starters, Jackson customization, removed annotations and package imports, container compatibility, and configuration properties. Keep business changes outside the upgrade diff.
Use the properties migrator temporarily, start each supported profile, and remove temporary migration aids before release. Run the project’s applicable unit, slice, integration and startup checks; include native and database migration checks where relevant. Compare HTTP/JSON contracts, security failure responses, actuator exposure and dependency graphs with the baseline. Report each check actually run, failures and checks that remain unverified.
Install only the migration skill folder, including its examples, into the chosen agent’s supported skill location. Upstream documents both Claude Code and Codex variants of its installation workflow; Multi-Framework describes these supported coding-agent hosts, while Spring Boot is the target application stack. This entry covers one application upgrade and its evidence, rather than the entire skill pack, an SDK integration, application scaffolding or deployment. Source metadata and documented invocation were inspected; this intake did not execute an application migration or perform a security review.