Skip to content
TrustedSkillsbeta
Back to all skills

Cucumber Best Practices

Listed
thebushidocollective·vlatest·testing

Ensures cucumber tests adhere to best practices – Gherkin clarity, step definition maintainability, and robust reporting.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add thebushidocollective/han --skill cucumber-best-practices -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

thebushidocollective

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: shop.com.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

    Hosts contacted

    shop.comundeclared

    What it found

    • plugins/tools/cucumber/skills/cucumber-best-practices/SKILL.md:21contacts shop.com
      Given I navigate to "http://shop.com/products"

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned thebushidocollective/han at 19caa51d5f.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
19caa51d5f
Manifest
plugins/tools/cucumber/skills/cucumber-best-practices/SKILL.md
Scanned
1 file, 416 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill helps you write better Cucumber tests by ensuring they adhere to best practices. It focuses on improving Gherkin scenario clarity, promoting maintainable step definitions, and enabling robust reporting. The skill guides you towards writing declarative scenarios that describe what needs to happen rather than how, ensures each scenario tests a single behavior, and promotes independent scenarios with their own preconditions.

When to use it

Here are some situations where this skill would be helpful:

  • You're new to Cucumber and want to learn best practices from the start.
  • Your existing Cucumber tests are difficult to understand or maintain.
  • You want to improve the clarity and readability of your feature files.
  • Scenarios are dependent on each other, leading to test fragility.
  • You're struggling to write scenarios that focus on business behavior rather than implementation details.

Key capabilities

  • Declarative Scenario Guidance: Helps you transform imperative (implementation-focused) scenarios into declarative (business-focused) ones.
  • Single Behavior per Scenario: Encourages writing separate scenarios for each distinct business rule or behavior.
  • Scenario Independence: Promotes setting up independent preconditions for each scenario to avoid dependencies.
  • Background Usage Guidance: Provides advice on the appropriate use of Background steps in Cucumber tests (though specific details are not provided).

Example prompts

Here are some example prompts you might give an AI agent with this skill installed:

  • "Review this Cucumber scenario and suggest improvements for clarity."
  • "How can I make this scenario more declarative?"
  • "This scenario seems to depend on a previous one. How can I make it independent?"

Tips & gotchas

  • The skill focuses on guiding you towards best practices; it doesn't automatically rewrite your Cucumber tests.
  • Pay close attention to the examples provided in the documentation to understand the difference between imperative and declarative scenarios.
  • Consider refactoring existing feature files incrementally, focusing on one scenario at a time.