Skip to content
TrustedSkillsbeta
Back to all skills

Cucumber Step Definitions

Checked
thebushidocollective·vlatest·testing

Generates reusable Cucumber step definitions for automated testing, streamlining test creation and improving maintainability.

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-step-definitions -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 passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • 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 undeclared network calls: passed

    Makes no network calls.

    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.

  • 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-step-definitions/SKILL.md
Scanned
1 file, 327 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 allows you to generate Cucumber step definitions from natural language descriptions. It automatically creates code snippets in a Gherkin-compatible format, streamlining the process of writing automated tests for software development projects. The generated steps are designed to be easily integrated into existing Cucumber test suites.

When to use it

  • You need to quickly create initial drafts of Cucumber step definitions for new features.
  • You're refactoring existing feature files and want to automate the generation of corresponding step definitions.
  • You’re onboarding a new team member unfamiliar with Cucumber syntax and want to accelerate their learning process.
  • You have a backlog of tests needing automation and need to expedite the creation of test code.

Key capabilities

  • Generates Cucumber step definitions from natural language input.
  • Supports Gherkin syntax for defining scenarios and steps.
  • Creates code snippets ready for integration into existing testing frameworks.

Example prompts

  • "Generate a step definition for 'Given the user is logged in'"
  • "Create a Cucumber step for 'When I click the submit button' that interacts with the UI."
  • “Write a step to verify ‘Then the confirmation message should display’ ”

Tips & gotchas

The quality of generated step definitions depends heavily on the clarity and specificity of your natural language input. Be as detailed as possible in your descriptions to ensure accurate code generation.