xpz-msbuild-import-export

Plan and execute XPZ import/export workflows via MSBuild with explicit parameters and safe gates.

11|3|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/GxBrasilNOficial/GeneXus-XPZ-Skills --skill xpz-msbuild-import-export
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: xpz-msbuild-import-export
Source: https://github.com/GxBrasilNOficial/GeneXus-XPZ-Skills/tree/main/xpz-msbuild-import-export
Command: npx skills add https://github.com/GxBrasilNOficial/GeneXus-XPZ-Skills --skill xpz-msbuild-import-export

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Este skill oferece operações de importação e exportação de XPZ via MSBuild, em execução sem interface gráfica, com rastreabilidade e gates de segurança. Não substitui o fluxo oficial atual da trilha paralela da KB, nem depende de GeneXus Server, e não trata sucesso operacional como evidência suficiente de sucesso funcional.

Core Features & Use Cases

  • Orquestra operações de XPZ via MSBuild com parâmetros explícitos, logs rastreáveis e validação da assinatura da task carregada.
  • Suporte a modo de visualização (PreviewMode) e, quando suportado pela task, atualização de arquivos (UpdateFile) antes da importação real.
  • Validação de segurança com gating, diagnóstico estruturado em JSON e registro completo de stdout/stderr/exitCode para auditoria.
  • Possibilita exportação/importação headless em KBs de teste controlados, com autorização explícita e controle de riscos.

Quick Start

Execute o fluxo de importação/exportação de XPZ via MSBuild com parâmetros explícitos para validar o ambiente e gerar o diagnóstico inicial.

Frequently Asked Questions about xpz-msbuild-import-export

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate XPZ import and export operations via MSBuild?

You automate XPZ import/export via MSBuild by orchestrating headless workflows with explicit parameters, traceable logs, and environment validation gates. This approach ensures controlled execution without a graphical interface.

Can I preview XPZ changes before committing an import to a controlled environment?

You can preview XPZ changes before importing by enabling PreviewMode. When supported, UpdateFile can also update files prior to the real import to help you validate modifications safely.

Does headless MSBuild XPZ export require GeneXus Server?

Headless MSBuild XPZ export does not require GeneXus Server. It operates independently via MSBuild scripts with explicit parameters, making it suitable for controlled test environments without server dependencies.

What is the safest way to run XPZ imports in production environments?

The safest way to run XPZ imports involves applying explicit authorization gates, validating the loaded task signature, and using controlled environments. Operational success alone is not treated as sufficient evidence of functional success.

How are MSBuild XPZ workflow errors diagnosed for auditing?

MSBuild XPZ workflow errors are diagnosed using structured JSON output and complete logging of stdout, stderr, and exitCode. This traceable audit data captures execution details for thorough post-run analysis.

Why should I use MSBuild for XPZ export instead of standard GUI workflows?

Using MSBuild for XPZ export provides headless execution, explicit parameter control, and safety gates that GUI workflows lack. It delivers traceable logs and structured JSON diagnostics necessary for automated CI pipelines.