testland/bdd-step-library-curator
Keeps a BDD step-definition library DRY across a Cucumber / Behave / Reqnroll project - inventories every step definition, detects duplicates (different patterns matching the same intent), recommends canonical consolidations, reorganizes steps by domain, publishes a step-library README the team greps for "is there already a step for X?" before authoring new ones, and builds a scenario coverage map that fingerprints new Gherkin scenarios against the live suite to classify each as duplicate, partial overlap, or genuine gap before any test is authored. Use when a BDD project's step count grows past ~50, on a quarterly step-library review, when a new engineer is about to write a duplicate step, or when fresh .feature files need a covered-already check.
73
92%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
1 low severity finding. Worth noting, but not necessarily harmful.
W011: Third-party content exposure detected (indirect prompt injection risk).
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
Step 1 and the coverage map workflow read step definitions and Gherkin `.feature` files from the project workspace (including newly landed feature files) to extract step texts and build fingerprints/indexes.
Where we found it
.feature (Gherkin feature files)
content-type · 3 sites
The plugin reads and parses Gherkin .feature files from the project workspace (both new and existing) to extract step texts, build fingerprints, and classify scenarios — these files could contain adversarial content from contributors.
references/coverage-map.md
Line 19
Line 36
SKILL.md
Line 165
step definition source files
content-type · 5 sites
The plugin reads step definition source files (Java, Python, C#) from the project workspace to extract step patterns for inventory and overlap detection — these files could contain adversarial content.
SKILL.md
39
Extract every declared step pattern across the project. Each runner uses its own annotation syntax
198
The Behave extraction over `features/steps/` yields the Step 1 audit
references/step-extraction-and-overlap.md
14
grep -rE '@(Given|When|Then|And|But)\(' src/test/java/
18
grep -rE '^@(given|when|then|step)\(' features/steps/
22
grep -rE '\[(Given|When|Then|And|But)\(' Tests/Steps/
Cucumber JSON report
content-type · 4 sites
The plugin optionally loads a Cucumber JSON report file from the workspace as an alternative data source for building the step-usage index, which could contain adversarial content in step texts or scenario titles.
references/coverage-map.md
Line 42
Line 48
Line 51
SKILL.md
Line 178
- Audited
- Security analysis