What problem does it solve?
Editing Gradle build scripts in the apache/grails-core monorepo is risky because the repo intentionally diverges from generic Gradle best practices: it uses composite builds, custom BOM platforms, convention plugins, presence-based flags, and heavy projectDir remapping. This Skill encodes those repo-specific rules so build changes are correct on the first try instead of breaking configuration, caching, or publishing.
Core Features & Use Cases
- Repo-specific build authoring: Write and modify build.gradle, settings.gradle, dependencies.gradle, and convention plugins exactly the way sibling modules do, including BOM platform() usage and the dependency-validator workflow.
- Multi-build topology guidance: Navigate the root build, build-logic, grails-gradle, grails-forge, and end-to-end builds, including the three-step local publish-and-test flow against build/local-maven.
- Gradle 9 hygiene enforcement: Avoid configuration-cache, afterEvaluate, task-input, and build-cache pitfalls documented from real production PRs.
- Use Case: When adding a new published module, follow the checklist to register it in settings.gradle, copy a sibling build script, wire the correct BOM platform, and run scoped compile, test, and validateDependencyVersions tasks.
Quick Start
Ask the assistant to add a new subproject or bump a dependency version in the grails-core repository following its Gradle conventions.
