We’re building Gradle agent skills
We have five candidates, but we’d rather ship the ones you’d actually use. Vote and tell us what’s missing.
1. Run Gradle correctly (gradle-cli) Right task, right flags, version-aware invocation, and reading the output properly.
2. Best-practices lint (gradle-best-practices) Scans build logic for legacy patterns — subprojects {}, deprecated APIs, misused configurations, no version catalog — and points to the current recommendation.
3. New project bootstrap (gradle-init) Working project from scratch: sensible defaults, version catalog, Develocity, starter layouts for Android / KMP / Spring.
4. Upgrade + deprecations (gradle-update) Bumps the wrapper, finds deprecated usages, rewrites them for the target version — including multi-version hops.
5. Configuration cache migration (gradle-cc) Finds what breaks the configuration cache (script-level state, Project access at execution time, non-serializable inputs) and refactors it.
Which would you use?
- gradle-cli
- gradle-best-practices
- gradle-init
- gradle-update
- gradle-cc
Votes are useful. Replies are more useful, especially if none of these are the thing you’d want first. If you’ve already tried handing Gradle work to an agent, we’d like to hear where it went wrong (or right).