hull lint

hull lint validates a package for correctness — metadata, values, schema, and a full render — and reports every problem it finds without touching a cluster.

When to use it

As a pre-commit or CI gate, before hull package or hull publish.
After editing values or templates, to confirm the package still renders.
With --strict when you want warnings (missing templates/, base overrides) to fail the build too.

What happens

Reads hull.yaml and checks its structure: apiVersion must be hull/v1, name is required, and version must be valid semver.
Parses values.yaml and values.schema.json (each optional) and reports any that is malformed.
Confirms templates/ exists and holds at least one .yaml file, warning if not.
If the structural checks passed, resolves layers, merges values (-f + --set + --profile), and renders every template; a render failure is reported as an error.
Checks that a declared base: exists and has its own hull.yaml, that a named --profile exists under profiles/, and warns on templates that override a base template.
Prints each finding as [ERROR] or [WARNING], then a final line. Exits non-zero on any error, or on any warning under --strict.

Usage

hull lint <package-path> [flags]

Purely local: lint never contacts a cluster, so the inherited --kube* flags have no effect here.

Flags

Flag	Type	Default	Description
`-f, --values`	stringArray	—	merge a values file before the render check, so lint sees the same values you deploy with (repeatable)
`--set`	stringArray	—	override one `key=value` before the render check (repeatable)
`--profile`	string	—	apply and validate the `profiles/<name>` overlay; a missing profile is an error
`--strict`	—	false	promote every warning to an error, so the command fails on warnings alone

Worked example

INPUT — the package ./web with one deliberate mistake. hull.yaml carries a version that is not valid semver:

# web/hull.yaml
apiVersion: hull/v1
name: web
version: "1.2"          # ← not semver; needs three components, e.g. 1.2.0

# web/values.yaml
replicas: 2

# web/templates/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: web
spec:
  replicas: ${values.replicas}

Run it:

hull lint ./web

OUTPUT:

[ERROR] hull.yaml: version "1.2" is not valid semver
Error: lint failed: 1 error(s), 0 warning(s)

The diagnostic points straight at the input: [ERROR] hull.yaml: names the file, and version "1.2" is not valid semver echoes the exact value that failed rule 1. The command exits non-zero, so a CI step stops here. Because a structural error was found, lint stops before the render check — fix the version and rerun to reach it.

Fix the version to a valid semver and lint passes:

version: 1.2.0

hull lint ./web

lint passed