plugins/dasel/skills/enterprise-maven-pom/SKILL.md
Dasel v3 selector patterns for Maven POM XML files — use when querying dependency versions, filtering by groupId or scope, extracting module hierarchy from parent POMs, or detecting version conflicts across enterprise multi-module Java projects. Load this skill when working with pom.xml files using dasel.
npx skillsauth add jamie-bitflight/claude_skills enterprise-maven-pomInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
<when_to_use>
Load this skill when querying any pom.xml file — extracting dependency versions, filtering by groupId or scope, mapping module hierarchy from parent POMs, or detecting version conflicts across a multi-module Java project.
</when_to_use>
Domain skill for querying Maven POM XML files using dasel v3. Always pass -i xml explicitly. Child element text content (groupId, artifactId, version, scope) is accessed by element name directly — no #text needed. Write intermediate batch results to /tmp/, never to the source tree.
# All dependency groupIds from a single POM
dasel -f pom.xml -i xml 'project.dependencies.dependency.map(groupId)'
Filter dependencies by groupId to isolate framework-specific versions.
# Spring dependency versions
dasel -f pom.xml -i xml 'project.dependencies.dependency.filter(groupId == "org.springframework").map(version)'
# Hibernate dependency versions
dasel -f pom.xml -i xml 'project.dependencies.dependency.filter(groupId == "org.hibernate").map(version)'
# Test-scoped dependency artifactIds
dasel -f pom.xml -i xml 'project.dependencies.dependency.filter(scope == "test").map(artifactId)'
# Compile-scoped dependencies (no scope element defaults to compile)
dasel -f pom.xml -i xml 'project.dependencies.dependency.filter(scope == "compile").map(artifactId)'
Extract module paths from a parent POM to map the project structure.
# Module list from parent POM
dasel -f pom.xml -i xml 'project.modules.module'
Batch pattern — iterate all POMs, extract dependencies per file, compare. Write results to /tmp/.
# Collect all dependency groupIds across every POM in the hierarchy
for pom in $(fdfind -e xml -n pom.xml .); do
echo "=== $pom ===" >> /tmp/all_deps.txt
dasel -f "$pom" -i xml 'project.dependencies.dependency.map(groupId)' >> /tmp/all_deps.txt 2>/dev/null
done
Inspect /tmp/all_deps.txt for the same groupId appearing with different versions across modules.
Extract groupId and artifactId together for dependency inventory.
# Dependency coordinates (groupId + artifactId) — run as two passes
dasel -f pom.xml -i xml 'project.dependencies.dependency.map(groupId)'
dasel -f pom.xml -i xml 'project.dependencies.dependency.map(artifactId)'
Enterprise POMs use dependencyManagement to declare BOM-controlled versions separately from active dependencies.
# Managed dependency versions (BOM section)
dasel -f pom.xml -i xml 'project.dependencyManagement.dependencies.dependency.map(version)'
# Active dependency versions (may be empty if version comes from BOM)
dasel -f pom.xml -i xml 'project.dependencies.dependency.map(version)'
development
When an application needs to store config, data, cache, or state files. When designing where user-specific files should live. When code writes to ~/.appname or hardcoded home paths. When implementing cross-platform file storage with platformdirs.
testing
Enforce mandatory pre-action verification checkpoints to prevent pattern-matching from overriding explicit reasoning. Use this skill when about to execute implementation actions (Bash, Write, Edit) to verify hypothesis-action alignment. Blocks execution when hypothesis unverified or action targets different system than hypothesis identified. Critical for preventing cognitive dissonance where correct diagnosis leads to wrong implementation.
tools
Reference guide for the Twelve-Factor App methodology — 15 principles (12 original + 3 modern extensions) for building portable, resilient, cloud-native applications. Use when evaluating application architecture, designing cloud-native services, reviewing codebases for methodology compliance, advising on configuration, scaling, observability, security, and deployment patterns. Incorporates the 2025 open-source community evolution and cloud-native reinterpretations of each factor.
tools
Converts user-facing documentation (how-to guides, tutorials, API references, examples) in any format — Markdown, PDF, DOCX, PPTX, XLSX, AsciiDoc, RST, HTML, Jupyter notebooks, man pages, TOML/YAML/JSON configs, and plain text — into Claude Code skill directories with SKILL.md plus thematically grouped references/*.md files. Use when given a docs directory or mixed-format documentation to transform into an AI skill. Uses MCP file-reader server for binary formats.