What problem does it solve?
Upgrading a Grails application from 7.x to Grails 8 involves breaking changes across Spring Boot 4.1, Spring Framework 7, Jackson 3, Hibernate 7, Gradle dependency management, content negotiation, and validation defaults, and missing any of them causes build failures or subtle runtime behavior changes.
Core Features & Use Cases
- Migration Checklist: Turns the official Grails 8 upgrade guide into an ordered, reversible workflow covering JDK, Gradle, BOM, configuration, and code changes.
- Breaking Change Reference: Documents Spring Boot 4 starter renames, Jackson 2-to-3 package moves, Hibernate 5 vs Hibernate 7 API replacements, TagLib and test annotation updates, and GORM nullable-default changes.
- Use Case: When reviewing a Grails 8 upgrade pull request, use this Skill to verify the build uses Gradle platform BOMs instead of the Spring dependency-management plugin, that
@MockBean was replaced with @MockitoBean, and that content negotiation behavior was tested with real browser requests.
Quick Start
Ask the assistant to walk through upgrading your Grails 7 application to Grails 8 and flag every breaking change in your build files, configuration, and code.