agentleFS
Sign inStart free
TiagoJacintoTiagoJacinto/skills/gherkin/SKILL.md

gherkin

Skill2 starsChanged 38 days agoMITView on GitHub

Shared Gherkin scenario rules. Use when authoring or reviewing .feature scenarios, including through ATDD or a custom Gherkin profile.

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use ordered phases: preconditions (Given) → one action (When) → observable outcomes (Then).

    line 10
  2. Distinctive:

    Write exactly one action per scenario.

    line 11
  3. Very specific:

    Use And and But to continue the current phase: additional preconditions under Given, or additional outcomes under Then.

    line 12

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Gherkin scenario structure

These rules apply to ordinary Gherkin and custom profiles. A profile defines its additional step syntax separately.

  • Use ordered phases: preconditions (Given) → one action (When) → observable outcomes (Then). Once a phase ends, continue forward rather than returning to it.
  • Write exactly one action per scenario. Split a flow that needs another action into separate scenarios.
  • Use And and But to continue the current phase: additional preconditions under Given, or additional outcomes under Then.
  • Distinguish state from input. State existed before the action and is independently observable; describe it under Given. Input is supplied for the action; describe it under When. Requests, commands, options, and expected values are inputs unless they were persisted before the action.
Scenario: Remove one stored variable
  Given APP_TOKEN is stored
  And SERVICE_KEY is stored
  When I remove APP_TOKEN
  Then APP_TOKEN is absent
  But SERVICE_KEY remains stored

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free