jamesfredley opened a new pull request, #16083:
URL: https://github.com/apache/grails-core/pull/16083
## Summary
Adds a **Gradle 9 developer skill** so agents write Gradle the way this
monorepo already does on `8.0.x`, instead of inventing generic Gradle patterns
that burn review cycles.
### Changes
1. **`.agents/skills/gradle-developer/SKILL.md`** - repo-first guidance
covering:
- Multi-build topology (`build-logic`, `grails-gradle`, `grails-forge`,
`end-to-end`, `gradle-bootstrap`)
- BOM / `platform()` dependency management and
`validateDependencyVersions` (direction-aware fixes)
- Convention plugin IDs (fully qualified)
- Wrapper sync via `gradle-bootstrap` + remaining locations (including
Forge generated-app resources)
- end-to-end 3-step flow (`build/local-maven` / TestCaseMavenRepo, legacy
G7 fixture, suite)
- Gradle 9 configuration hygiene from recent PRs (#15467, #16076, #16009,
#16006, #15763, etc.)
- Explicit **this repo wins over generic Gradle docs** table
2. **`AGENTS.md`** - mandatory skill bullet + skills table entry
### Notes
- Docs/skills only; no build or runtime code changes.
- Based on current `8.0.x` Gradle **9.6.0** layout and recent Gradle-related
PRs.
- Skill prefers established monorepo patterns when they conflict with
upstream Gradle recommendations (configuration cache off, no version catalogs,
no Spring DM plugin, etc.).
## Test plan
- [x] Spot-check skill claims against `settings.gradle`,
`dependencies.gradle`, `end-to-end/README.md`, `gradle-bootstrap`, and
convention plugins
- [x] Dual review-gate (oracle + codex) on both commits and the PR diff
- [ ] Human skim of skill for anything still wrong or missing for day-to-day
Gradle work
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
