agent-team-schema-export

To export a machine-readable CLI schema, run the schema export command to extract the command contract, version, and error catalog. This generates a structured output including command names, signatures, errors, and error recovery details for automated validation.

A CLI command contract is a machine-readable definition of command names, versions, signatures, and error catalogs. You need to export it when enforcing consistency across releases, validating the CLI surface in CI pipelines, or generating developer documentation.

Yes, you can integrate CLI schema export into CI pipelines to verify compatibility of the CLI surface during releases. The exported schema provides version-aware metadata and command signatures, enabling automated checks to enforce consistency across deployments.

The exported CLI schema data structure includes data.schema.command, data.schema.version, data.schema.commands, data.schema.errors, and data.schema.error_recovery. It also contains metadata.version and references to dependent skills and CLI entry points for comprehensive auditing.

Schema export requires no external dependencies or specific environment setup. It operates as a standalone CLI tooling feature to extract the command contract, allowing you to run the schema export command directly within your existing automation and auditing workflows.

Using a machine-readable schema export instead of manual documentation ensures synchronization across releases and enables automated validation. The exported contract provides a standardized format for command signatures and error catalogs, reducing human error and enforcing consistency for developers and operators.