Agent skill
Java Tooling Standards
Standards for build tools (Maven/Gradle) and static analysis.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/tooling-hoangnguyen0403-agent-skills-standar-2
Metadata
Additional technical details for this skill
- labels
-
java tooling maven gradle checkstyle
- triggers
-
{ "files": [ "pom.xml", "build.gradle", "build.gradle.kts" ], "keywords": [ "build", "dependency", "plugin", "sdk", "lint" ] }
SKILL.md
Java Tooling Standards
Priority: P2 (RECOMMENDED)
Standardized build and tooling configuration for consistent environments.
Implementation Guidelines
- JDK Management: Use
.sdkmanrcor.java-versionto lock JDK versions (Target LTS: 17 or 21). - Maven: Use
pom.xmlwith<dependencyManagement>for version control. Use wrapper (mvnw). - Gradle: Prefer Kotlin DSL (
build.gradle.kts). Use version catalogs (libs.versions.toml). Use wrapper (gradlew). - Linter: Use Spotless or Checkstyle (Google Style) to enforce formatting.
- Static Analysis: Integrate SpotBugs or SonarLint for deeper issue detection.
- Docker: Use multi-stage builds. Use
eclipse-temurinordistrolessimages.
Anti-Patterns
- Global Installs: Relying on system Maven/Gradle. Always use wrappers.
- Fat Jars: Avoid massive uber-jars if possible; prefer layered Docker images for caching.
- Snapshot Dependencies: Do not rely on
-SNAPSHOTversions in production builds.
Code
// build.gradle.kts (Gradle Kotlin DSL)
plugins {
java
id("com.diffplug.spotless") version "6.23.3"
}
java {
toolchain {
languageVersion.set(JavaLanguageVersion.of(21))
}
}
spotless {
java {
googleJavaFormat()
}
}
Related Topics
language | best-practices | testing
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?