112-java-maven-plugins
This Claude Code skill provides a structured, question-driven process for adding and configuring Maven plugins in pom.xml files. Use it when you need to integrate quality assurance tools like JaCoCo, SpotBugs, and PMD; security scanners like OWASP; build tools like Jib and Maven Compiler; or specialized profiles for mutation testing and benchmarking. The skill validates the project state first, analyzes existing configuration to avoid conflicts, and adds only the plugins you actually need while preserving existing setup.
git clone --depth 1 https://github.com/jabrena/cursor-rules-java /tmp/112-java-maven-plugins && cp -r /tmp/112-java-maven-plugins/skills/112-java-maven-plugins ~/.claude/skills/112-java-maven-pluginsSKILL.md
# 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 - Add Maven plugins in pom.xml - Improve Maven plugins in pom.xml ## Workflow 1. **Validate project before plugin changes** Run `./mvnw validate` or `mvn validate` and stop if validation fails. 2. **Analyze current plugin and profile configuration** Start with existing configuration analysis to identify what is already declared and avoid conflicts or replacement. 3. **Read plugin reference and collect selections** Read `references/112-java-maven-plugins.md`, then use a question-driven flow to select only needed plugins/profiles. 4. **Add non-conflicting plugin configuration** Add selected plugins and profiles without removing existing ones, preserving project structure and compatibility. 5. **Summarize applied plugin setup** Report added plugins/profiles, rationale, and recommended follow-up commands or checks. ## Reference For detailed guidance, examples, and constraints, see [references/112-java-maven-plugins.md](references/112-java-maven-plugins.md).
Use when you need to generate a checklist document with Java system prompts, following the embedded template exactly and producing INVENTORY-SKILLS-JAVA.md in the project root. This should trigger for requests such as Create Java system prompts checklist; Generate INVENTORY-SKILLS-JAVA.md; Use @001-skills-inventory. Part of cursor-rules-java project
Use when you need to generate a checklist document with embedded agents inventory, following the embedded template exactly and producing INVENTORY-AGENTS-JAVA.md in the project root. This should trigger for requests such as Create embedded agents inventory checklist; Generate INVENTORY-AGENTS-JAVA.md; Use @002-agents-inventory. Part of cursor-rules-java project
Use when you need to install the embedded robot agents into either .cursor/agents or .claude/agents, selecting the destination interactively and copying the embedded agent definitions from project assets. This should trigger for requests such as Install embedded agents; Bootstrap .cursor/agents; Bootstrap .claude/agents; Copy robot agents. Part of cursor-rules-java project
Guides the creation of agile epics with comprehensive definition including business value, success criteria, and breakdown into user stories. Use when the user wants to create an agile epic, define large bodies of work, break down features into user stories, or document strategic initiatives. This should trigger for requests such as Create an agile epic; Write an epic; I need to create an epic; Define an epic; Epic definition. Part of cursor-rules-java project
Guides the creation of detailed agile feature documentation from an existing epic. Use when the user wants to split an epic into feature files, derive features with scope and acceptance criteria, or plan feature documentation for stakeholders or engineering. This should trigger for requests such as Create features from an epic; Split epic into features; Feature files from epic; Derive features from epic. Part of cursor-rules-java project
Guides the creation of agile user stories and Gherkin feature files. Use when the user wants to create a user story, write acceptance criteria, define Gherkin scenarios, or author BDD feature files. This should trigger for requests such as Create a user story; Write a user story; I need to write a user story. Part of cursor-rules-java project
Use when you need to generate Architecture Decision Records (ADRs) for a Java project through an interactive, conversational process that systematically gathers context, stakeholders, options, and outcomes to produce well-structured ADR documents. This should trigger for requests such as Generate ADR; Create Architecture Decision Record; Document architecture decision; Architecture Decision Record for Java. Part of cursor-rules-java project
Facilitates conversational discovery to create Architectural Decision Records (ADRs) for functional requirements covering CLI, REST/HTTP APIs, or both. Use when the user wants to document command-line or HTTP service architecture, capture functional requirements, create ADRs for CLI or API projects, or design interfaces with documented decisions. This should trigger for requests such as Create ADR for functional requirements; Document functional requirements; Capture functional requirements; Generate functional requirements in an ADR. Part of cursor-rules-java project