Auditing Bdd Tests
CheckedThis skill audits your BDD tests for completeness and potential issues, ensuring robust test coverage and improved quality.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add viktor-silakov/bdd-best-practices --skill auditing-bdd-tests -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
viktor-silakov
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.
Automated safety checks
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 viktor-silakov/bdd-best-practices at c69fdc6061.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- c69fdc6061
- Scanned
- 13 files, 1,666 lines
About this skill
What it does
This skill analyzes Behavior Driven Development (BDD) test suites to identify potential issues and areas for improvement. It can examine Gherkin feature files, step definitions, and associated code to assess test coverage, redundancy, and adherence to BDD best practices. The goal is to ensure the tests are clear, maintainable, and effectively validate application behavior.
When to use it
- Refactoring a legacy BDD suite: Identify areas of technical debt or inconsistencies in an existing test framework.
- Onboarding new team members: Quickly assess the quality and structure of a project’s BDD tests for training purposes.
- Improving test maintainability: Pinpoint redundant steps, overly complex scenarios, or code smells within your BDD implementation.
- Ensuring consistent BDD style: Verify adherence to established coding standards and best practices across a team's BDD tests.
Key capabilities
- Gherkin syntax analysis
- Step definition mapping
- Redundancy detection
- Coverage assessment
- Best practice compliance checks
Example prompts
- "Analyze this Gherkin feature file for potential redundancies: [paste feature file content]"
- "Check the BDD test suite in this repository for adherence to best practices: [repository URL]"
- "Identify any steps that are duplicated across multiple scenarios."
Tips & gotchas
The skill's effectiveness depends on providing accurate and complete Gherkin files or access to a relevant code repository. It is designed primarily for standard BDD frameworks; custom implementations may require adjustments.