What problem does it solve?
Merging a previously standalone Grails plugin repository (such as grails-spring-security or grails-redis) into the grails-core monorepo involves dozens of error-prone steps: stripping duplicated build infrastructure, rewiring Gradle configuration, migrating documentation, and reproducing CI test matrices. This Skill provides a phased, checklist-driven process that prevents missed steps like lost RAT excludes, collapsed test matrices, or ungated publishing.
Core Features & Use Cases
- Phased merge process: Six phases covering history-preserving import, infrastructure port-or-delete decisions, Gradle build integration, documentation migration into the AsciiDoc guide, functional test app rewiring, and cleanup verification.
- Monorepo convention enforcement: Eliminates hard-coded dependency versions in favor of the Grails BOM, routes publishing through shared publish-config, merges plugin authors into PublishPlugin.groovy with emeritus classification, and registers coordinate renames in RENAME.md.
- CI and quality gating: Reproduces imported test matrices (e.g. TESTCONFIG variants), wires Testcontainers-based service dependencies, and ensures new test jobs block the publish job.
- Use Case: A maintainer importing grails-redis into grails-core follows the phases to subtree-merge the repo, delete its standalone gradle files, add modules to settings.gradle and publishedProjects, convert the README into a guide section, and verify with build, codeStyle, rat, and doc builds.
Quick Start
Ask the AI to merge the standalone grails-<name> plugin repository into the grails-core monorepo following the mono-repo-integration phased process, starting with a history-preserving import.
