plugins/dasel/skills/enterprise-spring-xml/SKILL.md
Dasel v3 selectors for Spring bean factory XML — use when querying any Spring ApplicationContext XML for bean discovery, dependency wiring, JMS destination mapping, property injection extraction, or cross-bean reference tracing. Load this skill before writing dasel selectors against Spring bean XML files (applicationContext.xml, *_beans.xml, spring-*.xml).
npx skillsauth add jamie-bitflight/claude_skills enterprise-spring-xmlInstall 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 Spring bean XML file — applicationContext.xml, *_beans.xml, spring-context.xml, or any Spring ApplicationContext XML — for bean discovery, dependency analysis, JMS wiring, property injection auditing, or cross-bean reference tracing.
</when_to_use>
Dasel v3 selector patterns for Spring bean factory XML. Always pass -i xml explicitly.
Attribute prefix rule: Dasel friendly mode (default) prefixes XML attributes with -. The id attribute is -id, class is -class. Text content is #text.
# All bean IDs
dasel -f chaosrouter_beans.xml -i xml 'beans.bean.filter(has("-id")).map("-id")'
# All bean classes
dasel -f chaosrouter_beans.xml -i xml 'beans.bean.filter(has("-class")).map("-class")'
# Map -class across every bean (includes beans without -id)
dasel -f chaosrouter_beans.xml -i xml 'beans.bean.map("-class")'
Filter beans by class name via regex on -class.
# Beans whose class contains JmsTemplate
dasel -f chaosrouter_beans.xml -i xml 'beans.bean.filter(-class ~ ".*JmsTemplate.*").map("-id")'
# Count beans matching a class pattern
dasel -f beans.xml -i xml 'len(beans.bean.filter(-class ~ ".*Jms.*"))'
Find beans referencing other beans via the -ref attribute on property child elements.
Pattern: parentCollection.filter(childElement.filter(condition).len($this) > 0) — filters the parent by testing whether a matching child exists (length > 0).
# Beans that reference a specific bean ID via ref attribute
dasel -f chaosrouter_beans.xml -i xml 'beans.bean.filter(property.filter(-ref == "targetBeanId").len($this) > 0).map("-id")'
Find which beans consume which JMS destinations via property child elements.
# Beans wired to a specific destination property
dasel -f integrationpoint_beans.xml -i xml 'beans.bean.filter(property.filter(-name == "destination").len($this) > 0).map("-id")'
Extract externalized ${...} placeholder values from bean definitions.
# All property values using ${...} placeholders
dasel -f storage_beans.xml -i xml 'beans.bean.property.filter(-value ~ ".*\\$\\{.*\\}.*").map("-value")'
# <bean id="myBean" class="com.example.Foo">some text</bean>
dasel -f beans.xml -i xml 'beans.bean[0].-id' # myBean
dasel -f beans.xml -i xml 'beans.bean[0].-class' # com.example.Foo
dasel -f beans.xml -i xml 'beans.bean[0].#text' # some text
# Discover all keys (attributes + child elements) on first bean
dasel -f beans.xml -i xml 'beans.bean[0].keys($this)'
Friendly mode strips namespace prefixes from element names — works for most Spring queries.
When namespace prefixes cause selector failures (element not found despite existing), switch to structured mode:
dasel -f spring-context.xml -i xml --read-flag xml-mode=structured 'beans.bean[0]'
Write intermediate results to /tmp/ — never to the source tree.
# Extract bean IDs from multiple files, compare
dasel -f chaosrouter_beans.xml -i xml 'beans.bean.filter(has("-id")).map("-id")' > /tmp/chaosrouter_beans.txt
dasel -f integrationpoint_beans.xml -i xml 'beans.bean.filter(has("-id")).map("-id")' > /tmp/integration_beans.txt
diff /tmp/chaosrouter_beans.txt /tmp/integration_beans.txt
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.