How do I install the 112 Java Maven Plugins skill?

Run npx skillmds add majiayu000/112-java-maven-plugins-3 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. Capability flags: docs only. 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, and the skill stays under its author's original license.

Who published 112 Java Maven Plugins?

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

112 Java Maven Plugins by majiayu000

Name: 112 Java Maven Plugins
Rating: 4.5 (4 reviews)
Author: majiayu000

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, build information tracking, and benchmarking (JMH) — through a consultative, modular step-by-step approach that only adds what you actually need.

majiayu000 812b948 2 files · 2.7 KB Updated Sep 9, 2026 567 repo stars

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.

Core areas: Existing configuration analysis and preservation, Maven Wrapper verification, project assessment questions (project nature, Java version, build and quality aspects), properties configuration, Maven Enforcer, Surefire, Failsafe, HTML test reports, JaCoCo coverage, PiTest mutation testing, OWASP security scanning, SpotBugs/PMD static analysis, SonarQube/SonarCloud, Spotless code formatting, Versions plugin, Git Commit ID, Flatten plugin, JMH benchmarking, Maven Compiler, and cyclomatic complexity analysis.

Prerequisites: Run ./mvnw validate or mvn validate before applying any plugin recommendations. If validation fails, stop and ask the user to fix issues — do not proceed until resolved.

Multi-step scope: Begin with Step 1 (existing configuration analysis) before any changes. Ask project assessment questions one-by-one in Step 3, then execute only the plugin steps relevant to user selections. Never remove or replace existing plugins; only add new ones that do not conflict.

Before applying changes: Read the reference for detailed plugin configurations, XML templates, and constraints for each step.

Reference

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

Frequently asked questions