How do I install the Java Tooling skill?

Run npx skillmds@latest add comeonoliver/java-tooling in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Java Tooling safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Java Tooling?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Java Tooling free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Java Tooling?

ComeOnOliver (@comeonoliver) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Java Tooling by comeonoliver — Agent Skill

Name: Java Tooling
Rating: 4.2 (5 reviews)
Author: ComeOnOliver

Java Tooling

Standards for Maven, Gradle, and static analysis in Java projects. Use when setting up Java build tooling, configuring Spotless or Checkstyle, managing JDK versions with sdkman, writing Dockerfiles for Java services, or adding SpotBugs/SonarLint. (triggers: pom.xml, build.gradle, build.gradle.kts, mvnw, gradlew, .sdkmanrc, spotbugs, checkstyle, spotless, eclipse-temurin)

ComeOnOliver Updated Sep 8, 2026 61 repo stars

File contents

Java Tooling Standards

Priority: P2 (RECOMMENDED)

Standardized build and tooling configuration for consistent environments.

Implementation Guidelines

JDK Setup: Use .sdkmanrc or .java-version to lock the project to LTS Support (17 or 21). Configure Gradle toolchain via java { toolchain { languageVersion = JavaLanguageVersion.of(21) } } for reproducible builds.
Maven & Wrapper: Use pom.xml with <dependencyManagement>. ALWAYS use the mvnw wrapper.
Gradle & Catalog: Prefer build.gradle.kts (Kotlin DSL) with libs.versions.toml (Version Catalog). Use the gradlew wrapper.
Formatting: Enforce Google Style Guide using Spotless (googleJavaFormat() plugin) or Checkstyle.
Static Analysis: Integrate SpotBugs or SonarLint for deep analysis. Use Detekt if using Kotlin.
Docker: Use Multi-stage Dockerfiles. Use eclipse-temurin as the base image.
CI/CD: Configure GitHub Actions or GitLab CI to run mvnw test or gradlew build on every PR.

Anti-Patterns

No Global Installs: Always use mvnw/gradlew wrappers; never rely on system Maven/Gradle.
No Fat Jars: Prefer layered Docker images over uber-jars for better layer caching.
No Snapshots in Prod: Never use -SNAPSHOT dependency versions in production builds.

References

Gradle Kotlin DSL & Spotless Setup

Frequently asked questions