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. This should trigger for requests such as Add Maven plugins in pom.xml; Improve Maven plugins
NewMaintained
Automatic
◆Coding pack
Last verified 8/20/2026
What it changes
Passed 15 of 20 test cases with the skill, and 17 of 20 without it.
Without skill86%
With skill73%
0 fixed16 passed either way3 still failing3 broke
Pass-rate lift
-14 pp
Tokens
+194%
Agent turns
0%
Response time
-26%
Model gemini-3.6-flashMeasured 8/20/2026v116 of 22 cases passed with skill · 20 comparable
Tokens, turns and time describe resource use, not a dollar price.
What's inside
The instructions your model reads when the skill loads.
SKILL.md259 lines20 files
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 READING PLUGIN REFERENCES: Run the question flow embedded in this SKILL.md first. Ask questions one-by-one in strict order, collect all selected plugins/profiles and conditional values, then read only the implementation references selected by the user's answers
Use when reviewing, improving, or refactoring Java object-oriented design, including applying SOLID, DRY, or YAGNI; improving classes and interfaces; correcting encapsulation, inheritance, or polymorphism; resolving God Class, Feature Envy, or Data Clumps; and improving object creation, methods, or exception contracts. Triggers include review Java OOD, refactor Java OOD, improve Java OOD, fix OOP misuse, and identify Java code smells. Part of Plinth Toolkit