build-tooling

To enforce Maven and Gradle wrapper usage, the Skill detects the build tool at task start and ensures wrapper execution to pin tool versions. It standardizes builds by verifying wrapper presence before tasks run across multi-module projects.

The best way to manage dependencies with BOMs in multi-module Java projects is using BOM-based dependency management and version properties. The Skill guides configurations to avoid inline versions, applying safe dependency practices across Maven and Gradle layouts.

Yes, you can use this build tooling with both Gradle Groovy and Kotlin DSLs. The Skill detects Gradle via build.gradle or build.gradle.kts files and supports various DSLs, handling configurations and conflicts across different repository layouts in multi-module projects.

Build tool detection handles conflicts by flagging them when both Maven and Gradle configurations exist in the repository. The Skill identifies Maven via pom.xml and Gradle via build.gradle files, alerting you to conflicting build setups before orchestrating tasks.

Yes, you need explicit version pinning when configuring compiler and test plugins in Java builds. The Skill guides plugin configuration for compiler, test, and code-quality tasks while satisfying requirements for version pinning and safe dependency management.