CommunitySchreiben & Editierengithub.com

Jamie-BitFlight/enterprise-spring-xml

Dasel v3-Selektoren für Spring Bean Factory XML — verwenden Sie dies, wenn Sie XML-Dateien des Spring ApplicationContext abfragen, um Beans zu entdecken, Abhängigkeiten zu verdrahten, JMS-Ziele zuzuordnen, Property-Injection zu extrahieren oder referenzübergreifende Bean-Tracing durchzuführen. Laden Sie dieses Skill, bevor Sie Dasel-Selektoren gegen Spring-Bean-XML-Dateien (applicationContext.xml, *_beans.xml, spring-*.xml) schreiben.

Was ist enterprise-spring-xml?

Dieser Skill bietet eine Sammlung leistungsstarker Dasel v3-Selektoren (einschließlich regulärer Ausdrücke und Filter) für die spezifische Abfrage von Spring-Bean-XML-Dateien wie applicationContext.xml und *_beans.xml. Er behandelt Bean-Erkennung, Klassenmustervergleich mit Regex, Abhängigkeitsanalyse über das `-ref`-Attribut, JMS-Zielzuordnung, Property-Injection-Extraktion und Attribut-/Textinhaltszugriff. Der Skill unterstützt die meisten Spring-Bean-Formate, erfordert das explizite Setzen von `-i xml` und enthält Richtlinien zur Handhabung von Namespace-Präfixen im friendly und structured Modus. Er ermöglicht plattformunabhängige Analysen (CLI-basiert), funktioniert mit beliebigen Spring-Anwendungskontext-XML-Dateien und bietet eine sichere Datei-handhabung, indem temporäre Ergebnisse im `/tmp/-`Verzeichnis gespeichert werden.

Funktioniert mit~Claude Code~Codex CLI~Cursor
npx skills add https://github.com/Jamie-BitFlight/claude_skills/tree/main/plugins/dasel/skills/enterprise-spring-xml

Installed? Explore more Schreiben & Editieren skills: steipete/notion, langchain-ai/langchain, bytedance/podcast-generation · View all 6 →

In Ihrer bevorzugten KI fragen

Öffnet einen neuen Chat, in dem dieser Agent-Skill bereits geladen ist.

Dokumentation

Spring Bean Factory XML — Dasel v3 Abfragemuster

<when_to_use>

Laden Sie dieses Skill, wenn Sie eine Spring-Bean-XML-Datei abfragen — applicationContext.xml, *_beans.xml, spring-context.xml oder eine andere Spring ApplicationContext-XML — für Bean-Erkennung, Abhängigkeitsanalyse, JMS-Verdrahtung, Property-Injection-Prüfung oder referenzübergreifendes Bean-Tracing.

</when_to_use>

Dasel v3-Selektormuster für Spring-Bean-Factory-XML. Immer explizit -i xml übergeben.

Attribut-Präfix-Regel: Der freundliche Modus von Dasel (Standard) stellt XML-Attributen ein - voran. Das id-Attribut wird zu -id, class zu -class. Textinhalt ist #text.

Bean-Erkennung

# Alle Bean-IDs
cat chaosrouter_beans.xml | dasel -i xml 'beans.bean.filter(has("-id")).map("-id")'

# Alle Bean-Klassen
cat chaosrouter_beans.xml | dasel -i xml 'beans.bean.filter(has("-class")).map("-class")'

# -class über jede Bean mappen (auch Beans ohne -id)
cat chaosrouter_beans.xml | dasel -i xml 'beans.bean.map("-class")'

Klassenmustervergleich

Filtern von Beans nach Klassennamen mittels Regex auf -class.

# Beans, deren Klasse JmsTemplate enthält
cat chaosrouter_beans.xml | dasel -i xml 'beans.bean.filter(-class ~ ".*JmsTemplate.*").map("-id")'

# Anzahl der Beans, die einem Klassenmuster entsprechen
cat beans.xml | dasel -i xml 'len(beans.bean.filter(-class ~ ".*Jms.*"))'

Abhängigkeitsanalyse

Finden von Beans, die andere Beans über das -ref-Attribut in property-Kind-Elementen referenzieren.

Muster: parentCollection.filter(childElement.filter(bedingung).len($this) > 0) — filtert das übergeordnete Element, indem geprüft wird, ob ein passendes Kindelement existiert (Länge > 0).

# Beans, die eine bestimmte Bean-ID über das ref-Attribut referenzieren
cat chaosrouter_beans.xml | dasel -i xml 'beans.bean.filter(property.filter(-ref == "targetBeanId").len($this) > 0).map("-id")'

JMS-Zielzuordnung

Finden, welche Beans welche JMS-Ziele über property-Kind-Elemente konsumieren.

# Beans, die an eine bestimmte Zieleigenschaft gebunden sind
cat integrationpoint_beans.xml | dasel -i xml 'beans.bean.filter(property.filter(-name == "destination").len($this) > 0).map("-id")'

Property-Injection-Extraktion

Extrahieren externalisierter ${...}-Platzhalterwerte aus Bean-Definitionen.

# Alle Property-Werte mit ${...}-Platzhaltern
cat storage_beans.xml | dasel -i xml 'beans.bean.property.filter(-value ~ ".*\\$\\{.*\\}.*").map("-value")'

Attribut- und Textinhaltszugriff

# <bean id="myBean" class="com.example.Foo">some text</bean>
cat beans.xml | dasel -i xml 'beans.bean[0].-id'       # myBean
cat beans.xml | dasel -i xml 'beans.bean[0].-class'    # com.example.Foo
cat beans.xml | dasel -i xml 'beans.bean[0].#text'     # some text

# Alle Schlüssel (Attribute + Kindelemente) auf der ersten Bean entdecken
cat beans.xml | dasel -i xml 'beans.bean[0].keys($this)'

Namespace-Handhabung

Der freundliche Modus entfernt Namespace-Präfixe von Elementnamen — funktioniert für die meisten Spring-Abfragen.

Wenn Namespace-Präfixe zu Selektionsfehlern führen (Element trotz Existenz nicht gefunden), wechseln Sie in den strukturierten Modus:

cat spring-context.xml | dasel -i xml --read-flag xml-mode=structured 'beans.bean[0]'

Dateiübergreifende Analyse

Zwischenergebnisse in /tmp/ schreiben — niemals im Quellverzeichnis.

# Bean-IDs aus mehreren Dateien extrahieren, vergleichen
cat chaosrouter_beans.xml | dasel -i xml 'beans.bean.filter(has("-id")).map("-id")' > /tmp/chaosrouter_beans.txt
cat integrationpoint_beans.xml | dasel -i xml 'beans.bean.filter(has("-id")).map("-id")' > /tmp/integration_beans.txt
diff /tmp/chaosrouter_beans.txt /tmp/integration_beans.txt

Individual skills in this repo

This repo contains 20 individual skills — each has its own dedicated page.

Jamie-BitFlight/agentskill-kaizen-meta-docs

Agentskill kaizen plugin documentation index. Load when needing to read about cross-platform notes, improvement plans, or DuckDB integration.

Jamie-BitFlight/bash-51-features

Bash 5.1 release features and improvements with practical examples. Use when working with Bash 5.1 features, epoch time variables, redirection enhancements, or when user asks about Bash 5.1 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-52-features

Bash 5.2 release features and improvements with practical examples. Use when working with Bash 5.2 features, variable handling enhancements, readline improvements, or when user asks about Bash 5.2 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-53-features

Bash 5.3 release features and improvements with practical examples. Use when working with Bash 5.3 features, new command substitution, GLOBSORT, loadable builtins, or when user asks about Bash 5.3 changes, new features, or version-specific capabilities.

Jamie-BitFlight/bash-development

This skill should be used when the user asks to "write a bash script", "create a shell script", "implement bash function", "parse arguments in bash", "handle errors in bash", or mentions bash development, shell scripting, script templates, or modern bash patterns.

Jamie-BitFlight/bash-lint

This skill should be used when the user asks to "lint bash script", "run shellcheck", "format shell script", "use shfmt", "fix shellcheck errors", or mentions shell script linting, formatting, code quality, or pre-commit hooks for bash.

Jamie-BitFlight/bash-logging

This skill should be used when the user asks to "add logging to bash script", "colorize output", "implement log levels", "CI/CD sections", "terminal colors in bash", or mentions logging functions, emoji output, collapsible CI sections, or shlocksmith.

Jamie-BitFlight/bash-portability

This skill should be used when the user asks about "POSIX compatibility", "portable shell scripts", "cross-shell compatibility", "bashisms", "shebang selection", or mentions writing scripts that work on different shells (bash, sh, dash, zsh) or different systems.

Jamie-BitFlight/bash-testing

This skill should be used when the user asks to "test bash script", "write shell tests", "use shunit2", "use shellspec", "create test suite for bash", or mentions unit testing, test frameworks, mocking, or test-driven development for shell scripts.

Jamie-BitFlight/brainstorming-skill

You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or when users request help with ideation, marketing, and strategic planning. Explores user intent, requirements, and design before implementation using research-validated prompt patterns.

Jamie-BitFlight/clang-format

Configure clang-format code formatting. Use when: user mentions clang-format or .clang-format, analyzing code style/patterns, creating/modifying formatting config, troubleshooting formatting, brace styles/indentation/spacing/alignment/pointer alignment, or codifying conventions.

Jamie-BitFlight/commitlint

When setting up commit message validation for a project. When project has commitlint.config.js or .commitlintrc files. When configuring CI/CD to enforce commit format. When extracting commit rules for LLM prompt generation. When debugging commit message rejection errors.

Jamie-BitFlight/conventional-commits

When writing a git commit message. When task completes and changes need committing. When project uses semantic-release, commitizen, git-cliff. When choosing between feat/fix/chore/docs types. When indicating breaking changes. When generating changelogs from commit history.

Jamie-BitFlight/dasel-reference

Use when querying, modifying, or converting JSON, YAML, TOML, XML, CSV, HCL, or INI with dasel v3. Complete reference for selectors, functions, conditionals, variables, spread operator, type casting, and format-specific patterns.

Jamie-BitFlight/data-exploration

Use when exploring unknown structured data files with dasel v3 — discover schema, list keys, find nested values, sample arrays, identify data types across JSON, YAML, TOML, XML, CSV, HCL, INI formats

Jamie-BitFlight/data-transformation

Use when modifying, converting, or transforming structured data with dasel v3 — in-place mutations, format conversion, batch operations, array manipulation, object construction, and merge patterns across JSON, YAML, TOML, XML, CSV, HCL, INI

Jamie-BitFlight/delegate

Decompose substantive work into phases, dispatch each phase to a sub-agent, and adjudicate what comes back. Use whenever a request asks for implementation, investigation, a fix, a review, or any change to files — including small ones — and whenever you are about to read source or run a diagnostic yourself instead of handing it off. Also use when a report from a sub-agent needs judging, when a phase needs re-dispatching, or when a user names one instance of a pattern. Does not apply when your own prompt begins "Your ROLE_TYPE is sub-agent." — then follow references/sub-agent-contract.md instead.

Jamie-BitFlight/enterprise-hibernate-hbm

Dasel v3 query patterns for Hibernate .hbm.xml mapping files — entity-table binding, Java property-to-column extraction, one-to-many set/list/bag relationship tracing, many-to-one foreign key discovery, batch scanning across 60+ HBM files. Use when querying Hibernate ORM class mappings, extracting schema metadata from Java persistence layer, or auditing entity-column relationships in enterprise legacy codebases.

Jamie-BitFlight/enterprise-installanywhere

Dasel v3 query patterns for InstallAnywhere .iap_xml installer definitions — use when querying action sequences, discovering variables, resolving platform conditions, navigating panels, or comparing installer variants. Files are 2.5+ MB, 65,000+ lines — too large for context reads, requires structural dasel queries.

Jamie-BitFlight/enterprise-maven-pom

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.

Verwandte Skills