AutoMax

Validate feature files against Gherkin syntax, the tag taxonomy, module rules and step definitions.

automax lint [paths...] [-p <slug>] [--undefined-steps] [--fix-tags] [--strict] [--file <path>]...

Flag	Meaning
`-p, --project <slug>`	project slug (default: every project)
`--undefined-steps`	also detect undefined steps through `bddgen` (slower)
`--fix-tags`	insert the layer or module tag suggested by a finding
`--strict`	treat warnings as errors
`--file <path>`	lint only this feature file; repeatable

Rules:

Rule	Severity
Gherkin parse error	error
not exactly one layer tag (`@ui`, `@api`, `@hybrid`)	error
not exactly one suite tag from `tags.suites`	error
`@user:`, `@data:`, `@env:`, `@har:`, `@skip:` value unknown to the project	error
`@jira:` / `@github:` pattern invalid	error
duplicate scenario titles in a feature	error
undefined step	error, only with `--undefined-steps`
Scenario Outline without a `# title-format:` comment	warning
unknown tag	warning
feature outside every declared module directory	warning
scenario lacks a tag its module expects	warning
unused step definition	warning

automax run lints first unless --no-lint is given. Exit code 3 on errors.

bun run automax lint -p demo-shop
bun run automax lint -p demo-shop --undefined-steps --strict