Use when upgrading an existing Spring Boot application to Boot 4 — dependency transitions, starter renames, test-annotation migration (e.g. @MockBean → @MockitoBean), Jackson 3 issues, related Spring Modulith 2 or Testcontainers 2 upgrade work, or planning a phased migration. Not for greenfield project creation or isolated repository design.
97
96%
Does it follow best practices?
Impact
99%
1.25xAverage score across 3 eval scenarios
Passed
No findings from the security scan
Spring Boot 3→4 migration plan and code changes
Scanner invoked
100%
100%
Target version 4.1.x
100%
100%
Web starter renamed
100%
100%
RestClient starter added
0%
100%
@MockBean replaced
100%
100%
@SpyBean replaced
100%
100%
Correct import package
100%
100%
@AutoConfigureMockMvc added
100%
100%
TestRestTemplate opt-in
100%
100%
TestConfig mock moved
100%
100%
Plan format sections
0%
100%
Per-phase status notes
100%
100%
Full-stack Spring Boot 4 migration plan and execution
Scanner run
100%
100%
Migration plan format
0%
60%
Upgrade order in plan
100%
100%
Spring Boot target version
100%
100%
Modulith version paired with Boot
100%
100%
Testcontainers artifact prefix
100%
100%
Event publication schema columns
100%
100%
Event publication backfill
0%
100%
Testcontainers import packages
100%
100%
Generic type removed
100%
100%
LocalStack string services
100%
100%
LocalStack getEndpoint
100%
100%
LocalStack image version
0%
100%
schema-initialization removed
100%
100%
Migrate Spring Retry to native resilience and HttpServiceProxyFactory to @ImportHttpServices
spring-retry removed
100%
100%
aspectj starter added
0%
100%
aop starter removed
0%
100%
EnableResilientMethods annotation
100%
100%
Resilience import in service
100%
100%
maxRetries parameter value
0%
100%
retryFor renamed to includes
100%
100%
Recover method removed
100%
100%
ImportHttpServices annotation
100%
100%
HttpServiceProxyFactory removed
100%
100%
Serviceclient base-url property
100%
100%
Phased migration report
100%
100%
6277c14
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.