What problem does it solve?
Enforcing code style and static analysis across 60+ grails-core modules produces scattered XML reports and cryptic violations. This Skill explains how to run the Grails code style and analysis Gradle plugins, interpret the aggregated Markdown violation reports, and fix each class of violation so builds stay clean before committing.
Core Features & Use Cases
- Violation Aggregation: Run
./gradlew aggregateViolations to execute Checkstyle, CodeNarc, PMD, and SpotBugs across every module and produce per-tool Markdown reports in build/reports/violations/.
- Guided Fixes: Provides rule-by-rule fix tables for common CodeNarc and Checkstyle violations, plus the
codenarcFix task for auto-fixable rules like UnnecessarySemicolon and UnnecessaryGString.
- Configuration Control: Documents every Gradle property for enabling opt-in tools (PMD, SpotBugs, Spotless), including test sources, and ignoring failures during report collection.
- Use Case: Before merging a pull request, run the aggregation task, auto-fix CodeNarc issues, manually resolve remaining Checkstyle import-order problems, and confirm each report reads
No violations found!.
Quick Start
Run the violation aggregation across all grails-core modules and help me interpret and fix the violations reported in the generated Markdown files.