Gherkin Desk

Paste one Cucumber or SpecFlow .feature file and run one of five jobs over it in the same sitting: audit the Gherkin against BDD authoring practice, rewrite it declaratively, find the edge cases, error states, boundaries and recovery paths it never covers, draft its step definitions in Ruby, JavaScript, Python or Java, or turn it into a manual QA test plan. A real Gherkin parser runs free in your browser first - 29 lint rules, canonical formatting with aligned Examples tables, step-signature analysis and undefined-step skeletons - and every flag it raises comes back reconciled, confirmed or cleared with a reason. Derived from @el-feo/cucumber-gherkin, @thebushidocollective/bdd-patterns, @product-on-purpose/deliver-edge-cases and @phuryn/test-scenarios.

Every public app is built from a security-scanned skill and must pass a clean scan — skill and frontend — before it can be listed. Have a skill of your own? Turn it into an app — or read the step-by-step walkthrough.