$ cue help vet
The vet command validates CUE and other data files.
The command is silent when it succeeds; otherwise it reports any errors found.

Input arguments can be CUE packages, CUE files, non-CUE files, or some
combinations of those. See "cue help inputs" for more detail.

By default, vet ensures that the result of validation is concrete
by reporting an error if any resulting regular fields have non-concrete values.
Use -c=false to not require concreteness, or -c to show these error messages.

vet can also validate non-CUE files in these file formats:

  Format       Extensions
	JSON       .json .jsonl .ndjson
	YAML       .yaml .yml
	TOML       .toml
	TEXT       .txt  (validate a single string value)

Data files with multiple values, such as YAML with --- document separators,
are validated one object at a time. Use --list to validate them as a list.

By default, each file is checked against the root of the loaded CUE.
Use the -d flag to select a schema at a particular expression instead.

Examples:

  # Check that a collection of CUE packages has no errors.
  cue vet -c=false ./...

  # Check against a schema at the root of a CUE file:
  cue vet -c foo.cue foo.yaml

  # Check against a schema from a registry:
  cue vet -c -d '#Workflow' cue.dev/x/githubactions@latest workflow.yml

The -d flag can be repeated to validate against multiple schemas at once.

Usage:
  cue vet [flags] [inputs]

Flags:
  -c, --concrete[=true|false]       require the evaluation to be concrete, or set -c=false to allow incomplete values
  -t, --inject stringArray          set the value of a tagged field
  -T, --inject-vars[=true|false]    inject system variables in tags
      --language-version string     fallback language version for input outside a module (for example, v0.17.0)
      --list[=true|false]           concatenate multiple objects into a list
      --merge[=true|false]          merge non-CUE files (default true)
  -p, --package string              package name for non-CUE files and CUE output
  -l, --path stringArray            CUE expression for single path component (see 'cue help flags' for details)
      --proto_enum string           mode for rendering enums (int|json) (default "int")
  -I, --proto_path stringArray      paths in which to search for imports
  -d, --schema stringArray          expression to select schema for evaluating values in non-CUE files
      --with-context[=true|false]   import as object with contextual data (see 'cue help flags' for details)

Global Flags:
  -E, --all-errors[=true|false]   print all available errors
  -C, --chdir string              change working directory before running command (must be the first flag)
  -i, --ignore[=true|false]       proceed in the presence of errors