--- name: pom-ordering description: Enforce Maven POM dependency ordering rules. This skill should be used when editing pom.xml files. --- ## Ordering Rules First, group dependencies by scope (compile, runtime, test). Within each scope, group by groupId in this order: 1. First-party (${project.groupId} or modules within the project) 2. cool.klass 3. io.liftwizard 4. org.eclipse.collections 5. io.dropwizard 6. Other third-party libraries 7. Jakarta ## Region Comment Structure Use region comments for each groupId+scope combination: - `` - `` - `` - `` - `` - `` - `` (for other dependencies) - `` - `` Close each region with `` Within some groups, use nested regions for further organization: - For io.liftwizard runtime: `` then `` - For io.dropwizard: core modules first, then specialized modules ## Example Structure ```xml ${project.groupId} example-services ${project.version} ${project.groupId} example-domain-model ${project.version} runtime io.liftwizard liftwizard-graphql-reladomo-meta runtime io.liftwizard liftwizard-bundle-cors runtime io.liftwizard liftwizard-config-logging-logstash-console runtime org.junit.jupiter junit-jupiter test ```