eliteforge-new-java-maven-model

Generate and wire a Java Maven model module from the root pom.xml description.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/CloudSen/eliteforge-skills --skill eliteforge-new-java-maven-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: eliteforge-new-java-maven-model
Source: https://github.com/CloudSen/eliteforge-skills/tree/main/skills/eliteforge-new-java-maven-model
Command: npx skills add https://github.com/CloudSen/eliteforge-skills --skill eliteforge-new-java-maven-model

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This skill generates and wires a new Java Maven model module for a multi-module project by reading the repository root pom.xml description to extract company name, product name, and service name, then creates a module named <serviceName>-<modelName> with a pom.xml, package path, artifactId, and groupId, and updates the parent pom.xml modules accordingly. If the parent pom.xml already manages dependencies for the same family, it also syncs internal dependency management entries.

Core Features & Use Cases

  • Automatically derives module name, package, artifactId, and groupId from the root pom description and scaffolds the module under the repository root.
  • Updates the parent pom.xml to include the new module and, if applicable, inserts managed dependencies following existing conventions.
  • Provides a safe workflow with a dry-run option to preview changes before applying, and builds a minimal skeleton with .gitkeep files to ensure Git tracking.
  • Enforces the gating condition: the skill only runs when the user explicitly states the project adheres to the "璀璨工坊规范" or "eliteforge specification".

Quick Start

Run the scaffold_java_maven_model.py script with a model name to generate a new service-model module from the repository root pom description.

Frequently Asked Questions about eliteforge-new-java-maven-model

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

FAQPage Schema
How do I create a new Maven model module from a root pom.xml in a multi-module Java project?

To create a Maven model module from a root pom.xml, this skill reads the repository description to extract company, product, and service names, then scaffolds the module with the correct pom.xml, package, artifactId, and groupId. It also updates the parent pom.xml modules list.

What is dependency management synchronization when adding a new Maven module?

Dependency management synchronization in Maven modules ensures that when a new model module is created, its dependencies are automatically added to the parent pom.xml's dependencyManagement section if the parent already manages dependencies for the same family.

How do I scaffold a Java Maven module with specific artifactId and groupId naming conventions?

Scaffolding a Java Maven module with specific naming conventions is done by deriving the artifactId and groupId directly from the root pom.xml description. The script creates a <serviceName>-<modelName> module and initializes the package path accordingly.

Does this Maven module scaffolding tool require a specific project specification to run?

Yes, this Maven module scaffolding tool requires explicit confirmation that your project adheres to the "璀璨工坊规范" or "eliteforge specification". This gating condition ensures the module generation follows your established architectural standards.

Can I preview Maven pom.xml changes before generating a new module?

Yes, you can preview Maven pom.xml changes before generating a new module by using the built-in dry-run option. This allows you to safely review the parent pom.xml updates and dependency management insertions before applying any modifications.

Why are .gitkeep files added to the skeleton of a newly generated Maven module?

.gitkeep files are added to the skeleton of a newly generated Maven module to ensure Git tracks the otherwise empty directories. This guarantees that the minimal module structure is properly committed to version control immediately after scaffolding.