How do I install the 112 Java Maven Plugins skill?

Run npx skillmds@latest add jabrena/112-java-maven-plugins-2 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 112 Java Maven Plugins safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with 112 Java Maven Plugins?

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 112 Java Maven Plugins free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published 112 Java Maven Plugins?

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

112 Java Maven Plugins by jabrena — Agent Skill

Name: 112 Java Maven Plugins
Author: jabrena

112 Java Maven Plugins

Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. Part of the skills-for-java project

jabrena Updated Sep 22, 2026

File contents

Maven Plugins: pom.xml Configuration Best Practices

Configure Maven plugins and profiles in pom.xml using a structured, question-driven process that preserves existing configuration. This is an interactive SKILL.

What is covered in this Skill?

Maven plugins:

Maven Compiler
Maven Enforcer
Maven Surefire
Maven Failsafe
HTML test reports (Surefire Report, JXR)
Maven Spotless
Maven Flatten
Maven Versions
Maven Git Commit ID
Maven Jib

Maven profiles:

JaCoCo (code coverage)
PiTest (mutation testing)
Security (OWASP dependency check)
Static analysis (SpotBugs, PMD)
SonarQube/SonarCloud
JMH (Java Microbenchmark Harness)
Cyclomatic complexity

Constraints

Before applying plugin recommendations, ensure the project is in a valid state. Use a structured, question-driven process that preserves existing configuration and adds only what the user selects.

MANDATORY: Run ./mvnw validate or mvn validate before applying any plugin recommendations
SAFETY: If validation fails, stop and ask the user to fix issues—do not proceed until resolved
SCOPE: Begin with Step 1 (existing configuration analysis) before any changes. Never remove or replace existing plugins; only add new ones that do not conflict
BEFORE APPLYING: Read the reference for detailed plugin configurations, XML templates, and constraints for each step

When to use this skill

Configure Maven plugins in pom.xml
Add Maven plugins to pom.xml
Improve Maven plugins configuration in pom.xml

Reference

For detailed guidance, examples, and constraints, see references/112-java-maven-plugins.md.

---name: 112-java-maven-plugins-2description: Use when you need to add or configure Maven plugins in your pom.xml — including quality tools (enforcer, surefire, failsafe, jacoco, pitest, spotbugs, pmd), security scanning (OWASP), code formatting (Spotless), version management, container image build (Jib), build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need. Part of the skills-for-java projectlicense: Apache-2.0---# Maven Plugins: pom.xml Configuration Best PracticesConfigure Maven plugins and profiles in pom.xml using a structured, question-driven process that preserves existing configuration. **This is an interactive SKILL**.**What is covered in this Skill?**Maven plugins:- Maven Compiler- Maven Enforcer- Maven Surefire- Maven Failsafe- HTML test reports (Surefire Report, JXR)- Maven Spotless- Maven Flatten- Maven Versions- Maven Git Commit ID- Maven JibMaven profiles:- JaCoCo (code coverage)- PiTest (mutation testing)- Security (OWASP dependency check)- Static analysis (SpotBugs, PMD)- SonarQube/SonarCloud- JMH (Java Microbenchmark Harness)- Cyclomatic complexity## ConstraintsBefore applying plugin recommendations, ensure the project is in a valid state. Use a structured, question-driven process that preserves existing configuration and adds only what the user selects.- **MANDATORY**: Run `./mvnw validate` or `mvn validate` before applying any plugin recommendations- **SAFETY**: If validation fails, stop and ask the user to fix issues—do not proceed until resolved- **SCOPE**: Begin with Step 1 (existing configuration analysis) before any changes. Never remove or replace existing plugins; only add new ones that do not conflict- **BEFORE APPLYING**: Read the reference for detailed plugin configurations, XML templates, and constraints for each step## When to use this skill- Configure Maven plugins in pom.xml- Add Maven plugins to pom.xml- Improve Maven plugins configuration in pom.xml## ReferenceFor detailed guidance, examples, and constraints, see [references/112-java-maven-plugins.md](references/112-java-maven-plugins.md).

Frequently asked questions