Gherkin Formatter

The tool accepts Gherkin feature files or snippets and outputs a canonical, consistently formatted version. It identifies features, scenarios, steps, and backgrounds, and applies uniform indentation, line breaks, and keyword casing. The formatter normalizes whitespace and compresses excessive blank lines, ensuring identical structure across repositories. It preserves comments and ensures samples remain executable by Cucumber and similar engines when used with standard dialects.
Conceptually, it treats Gherkin as a structured DSL and enforces shared style rules that minimize interpretation differences across teams. It supports common features such as Scenario Outline, Examples tables, and Background clauses, while enforcing a consistent treatment of Given/When/Then keywords. The tool benefits developers, QA engineers, product owners, and technical writers who collaborate on behavior-driven development, validation, and documentation workflows.
Core features include input normalization, keyword alias handling, optional tags, and line-ending consistency. It provides deterministic output suitable for diffs and version control, and it can be run locally or via API in automation pipelines. Use cases include preparing feature files for CI checks, generating tutorials with clean samples, auditing repositories for style drift, and onboarding new team members with a standardized baseline.