Communitygithub.com

Jamie-BitFlight/enterprise-installanywhere

Dasel v3-Abfragemuster für InstallAnywhere .iap_xml-Installationsdefinitionen – verwenden Sie diese beim Abfragen von Aktionssequenzen, Entdecken von Variablen, Auflösen von Plattformbedingungen, Navigieren in Panels oder Vergleichen von Installationsvarianten. Dateien sind 2,5+ MB groß, 65.000+ Zeilen – zu groß für Kontext-Lesevorgänge, erfordert strukturelle Dasel-Abfragen.

Was ist enterprise-installanywhere?

Dieses Skill bietet ein strukturiertes Set an Dasel v3-Abfragemustern für InstallAnywhere `.iap_xml`-Dateien. Es ist für Entwickler und DevOps-Ingenieure konzipiert, die große Installationsdefinitionen (2,5+ MB, 65.000+ Zeilen) analysieren müssen, ohne die Datei vollständig in den Kontext eines KI-Assistenten laden zu können. Der Skill beschreibt die spezifischen Dasel-Abfragen, um die Wurzelstruktur (`InstallAnywhere.project`), Aktionssequenzen, Variablendefinitionen, plattformspezifische Bedingungen (z. B. Windows vs. Linux), Panel-Navigation, Dateikopiervorgänge und den Vergleich zwischen verschiedenen Installationsvarianten (z. B. RA vs. NON_RA) zu untersuchen. Er betont die Verwendung von strukturellen benannten Suchmustern (`..elementName`, `search(has())`) und die Ausgabe von Zwischenergebnissen in `/tmp/`. Der Skill ist für den Einsatz mit Dasel v3 optimiert, wobei die `-i xml`-Option explizit angegeben werden muss.

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

In Ihrer bevorzugten KI fragen

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

Dokumentation

InstallAnywhere .iap_xml Abfragemuster

<when_to_use>

Laden Sie diesen Skill, wenn Sie mit einer .iap_xml-Datei arbeiten – zum Prüfen von Installationsaktionen, Auflisten von Dateikopiervorgängen, Entdecken von Variablen, Finden plattformspezifischer Verzweigungen oder Vergleichen zweier Installationsvarianten (z. B. RA vs. NON_RA-Builds).

</when_to_use>

Betriebliche Einschränkungen

  • Übergeben Sie immer explizit -i xml – die automatische Erkennung schlägt bei .iap_xml-Erweiterungen fehl
  • Schreiben Sie alle Zwischenergebnisse nach /tmp/ – niemals in den Quellbaum
  • Dateien sind 2,5–2,6 MB groß, 65.000+ Zeilen – verwenden Sie strukturelle Dasel-Abfragen, lesen Sie die Datei niemals vollständig in den Kontext

Root-Struktur

InstallAnywhere .iap_xml-Dateien haben einen festen Root-Pfad: InstallAnywhere.project.

# Namen der Elemente der obersten Ebene im Dokument-Root
cat installer.iap_xml | dasel -i xml 'keys($this)'

# Navigieren zur Installationsaktionssequenz
cat installer.iap_xml | dasel -i xml 'InstallAnywhere.project.installSequence'

# Kinder des Projektknotens
cat installer.iap_xml | dasel -i xml 'InstallAnywhere.project.keys($this)'

Rekursiver Abstieg – findet Elemente in beliebiger Tiefe, ohne den vollständigen Pfad zu kennen:

# Alle Elemente namens "action" in beliebiger Tiefe
cat installer.iap_xml | dasel -i xml '..action'

# Alle Elemente namens "panel" in beliebiger Tiefe
cat installer.iap_xml | dasel -i xml '..panel'

# Jeder Knoten in beliebiger Tiefe, bei dem ein bestimmtes Attribut existiert
cat installer.iap_xml | dasel -i xml 'search(has("-name"))'

..elementName steigt rekursiv ab. search(predicate) findet Knoten in beliebiger Tiefe.

Aktionssequenzanalyse

# Alle Aktionsnamen in Ausführungsreihenfolge
cat installer.iap_xml | dasel -i xml '..action.map("-name")'

# Alle Aktionstypen
cat installer.iap_xml | dasel -i xml '..action.map("-type")'

# Anzahl aller Aktionselemente
cat installer.iap_xml | dasel -i xml 'len(..action)'

# Zur Analyse schreiben
cat installer.iap_xml | dasel -i xml '..action.map("-name")' > /tmp/action_names.txt
cat installer.iap_xml | dasel -i xml '..action.map("-type")' > /tmp/action_types.txt

Variablenentdeckung

# Alle Variablendefinitionen
cat installer.iap_xml | dasel -i xml '..variable.map("-name")' > /tmp/installer_vars.txt

Plattformbedingungen

# Alle Plattformbedingungen (Windows vs Linux-Verzweigungen)
cat installer.iap_xml | dasel -i xml 'search(has("-platform")).map("-platform")' > /tmp/platforms.txt

Variantenübergreifender Vergleich

Beim Vergleichen zweier Builds desselben Installers (z. B. RA vs. NON_RA, Windows vs. Linux-Variante):

# Aktionssätze zwischen zwei Installer-Dateien vergleichen
cat installer_a.iap_xml | dasel -i xml '..action.map("-name")' | sort > /tmp/actions_a.txt
cat installer_b.iap_xml | dasel -i xml '..action.map("-name")' | sort > /tmp/actions_b.txt
diff /tmp/actions_a.txt /tmp/actions_b.txt > /tmp/installer_diff.txt

# Panelsätze vergleichen
cat installer_a.iap_xml | dasel -i xml '..panel.map("-name")' | sort > /tmp/panels_a.txt
cat installer_b.iap_xml | dasel -i xml '..panel.map("-name")' | sort > /tmp/panels_b.txt
diff /tmp/panels_a.txt /tmp/panels_b.txt

Dateikopiervorgänge

# Alle Dateikopierquellen
cat installer.iap_xml | dasel -i xml '..installFile.map("-source")' > /tmp/file_copies.txt

Panel-Navigation

# Panelnamen und -anzahl
cat installer.iap_xml | dasel -i xml '..panel.map("-name")'
cat installer.iap_xml | dasel -i xml 'len(..panel)'

Attribut-Syntax-Referenz

XML-Attribute verwenden das --Präfix im Dasel-Freundlich-Modus:

# Zugriff auf ein bestimmtes Attribut beim ersten Treffer
cat installer.iap_xml | dasel -i xml '..action[0].-name'

# Attribute und Kinder eines Knotens entdecken
cat installer.iap_xml | dasel -i xml '..action[0].keys($this)'

# Attributwerte über alle passenden Knoten extrahieren
cat installer.iap_xml | dasel -i xml '..elementName.map("-attributeName")'

# Zählen passender Elemente
cat installer.iap_xml | dasel -i xml 'len(..elementName)'

# Suche mit Attributprädikat in beliebiger Tiefe
cat installer.iap_xml | dasel -i xml 'search(has("-attributeName"))'

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-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.

Jamie-BitFlight/enterprise-spring-xml

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).

Verwandte Skills