build-conventions

Name: build-conventions
Availability: InStock
Author: jsamuelsen11

Standardize Java project builds with Gradle Kotlin DSL and Maven conventions.

Updated Feb 7, 2026

Search Tags:#java #code-quality #maven #gradle #dependency-management #build-conventions

Ready to run

npx skills add https://github.com/jsamuelsen11/claude-config --skill build-conventions

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: build-conventions
Source: https://github.com/jsamuelsen11/claude-config/tree/main/plugins/ccfg-java/skills/build-conventions
Command: npx skills add https://github.com/jsamuelsen11/claude-config --skill build-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardize Java project builds by providing conventions for Gradle Kotlin DSL, Maven POM configurations, dependency management, plugin usage, multi-module layouts, and overall build performance.

Core Features & Use Cases

Gradle and Maven Standardization: Establishes consistent syntaxes and project layouts for Gradle (Kotlin DSL) and Maven builds, including plugin and dependency management.
Dependency Management and BOMs: Enforces centralized version control, proper BOM usage, and clear dependency scopes to ensure compatibility.
Quality and Performance Tooling: Integrates code formatting, static analysis, test coverage, and build performance practices (Spotless, Checkstyle, SpotBugs, JaCoCo, build caching) to improve reliability.

Quick Start

Create a new Java project and apply the build-conventions template to Gradle or Maven to align your project with standard Java build practices.

Frequently Asked Questions about build-conventions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I standardize Java build configurations across multiple projects?▼

Standardize Java build configurations by applying consistent Gradle Kotlin DSL or Maven POM setups, enforcing centralized BOM dependency management, and integrating quality tools to maintain uniform project layouts across single-module and multi-module builds.

What is the best way to enforce code quality and formatting in a Gradle Kotlin DSL build?▼

Enforce code quality in a Gradle Kotlin DSL build by integrating static analysis and formatting tools like Spotless, Checkstyle, SpotBugs, and JaCoCo to automate checks, validate code standards, and track test coverage reliably.

Does this build-conventions approach support both Maven and Gradle for multi-module setups?▼

This approach supports both Maven and Gradle for multi-module setups, providing standardized project layouts, centralized dependency scopes, and consistent plugin management to ensure compatibility and maintainability across diverse modules.

How do I centralize dependency versions and scopes in a Java project?▼

Centralize dependency versions and scopes in a Java project by enforcing Bill of Materials (BOM) usage, which aligns library versions across single and multi-module builds to prevent conflicts and ensure strict dependency compatibility.

Can I integrate static analysis and test coverage tools into my existing Maven build?▼

You can integrate static analysis and test coverage tools into an existing Maven build by applying standardized conventions that wire Checkstyle, SpotBugs, and JaCoCo directly into your POM configuration for automated quality checks.

What are the limitations of manually configuring Gradle and Maven builds without standard conventions?▼

Manually configuring Gradle and Maven builds without standard conventions leads to inconsistent project layouts, dependency version conflicts, and fragmented quality tooling, which degrades overall build performance and codebase maintainability.