Review Gradle build logic diffs for Spine conventions and best practices.
npx skills add https://github.com/SpineEventEngine/config --skill gradle-review
Please help me install this Agent Skill. Skill: gradle-review Source: https://github.com/SpineEventEngine/config/tree/main/.agents/skills/gradle-review Command: npx skills add https://github.com/SpineEventEngine/config --skill gradle-review
It prevents Gradle build failures and performance/correctness regressions by reviewing Gradle task and plugin code for compliance with Spine and upstream best practices.
group = "spine" and a correct imperative description.Provider.get() during configuration, eager FileCollection/Configuration resolution, wrong output wiring).config repository buildSrc/ (with a carve-out for module.gradle.kts), Gradle scripts in the consuming project, and production code for Gradle plugins.Run the gradle-review skill against your staged diff to get a categorized report of Must fix, Should fix, and Nit findings.
High-intent search queries and answers about installing and using this skill.
Gradle build logic review checks task and plugin code diffs against Spine SDK conventions and upstream best practices. It enforces required task metadata, flags eager resolution patterns, and reports categorized findings without running builds.
Custom Gradle plugin tasks should set `group = "spine"` and include a correct imperative `description`. This review verifies every custom task meets these metadata requirements to ensure build logic conformance before you open a PR.
Calling Provider.get() during configuration forces eager resolution, breaking Gradle's lazy evaluation and configuration cache. This review flags such correctness-breaking patterns in buildSrc and plugin code diffs to prevent performance regressions.
Yes, the review scopes across `buildSrc/` distributed configuration code, project Gradle scripts, and Gradle plugin production code. It applies specifically to diffs that register or configure tasks, excluding `module.gradle.kts` by default.
Yes, the review analyzes staged diffs statically to report Must fix, Should fix, and Nit findings with file and line citations. It detects incorrect output wiring and convention violations without executing the build.
You should avoid running a Gradle build logic review when your changes do not touch Gradle build scripts, `buildSrc/`, or plugin task registration code. The review is focused exclusively on Gradle-related diffs and will not analyze unrelated source code.
joaquimscostaDiagnose Spring Boot 4.x migration gaps in Maven and Gradle projects.
ClankerGuruOrganize Gradle task definitions with lazy registration and input/output metadata.
lhotariAnalyze failing GitHub Actions CI logs and test reports for Maven or Gradle Java projects.
nicolanoviellReview code changes for bugs, style issues, and best practices.