review-feature-suite

Audits and reconciles multiple Gherkin feature files for cross-file consistency.

Updated Apr 12, 2026
One-click install
npx skills add https://github.com/azborgonovo/ai-skills --skill review-feature-suite-azborgonovo
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-feature-suite
Source: https://github.com/azborgonovo/ai-skills/tree/main/skills/bdd/review-feature-suite
Command: npx skills add https://github.com/azborgonovo/ai-skills --skill review-feature-suite-azborgonovo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? A BDD suite can have individually correct feature files that still contradict each other, duplicate steps, or use different words for the same concept. This Skill audits an entire suite of .feature files as one corpus, finds the inconsistencies, and reconciles them with your input. ## Core Features & Use Cases - Cross-file consistency audit: Detects synonym drift, duplicated or near-duplicate steps, contradictory scenarios, orphaned preconditions, and tag or naming inconsistencies across all feature files. - Ambiguity resolution before edits: Asks which synonym is canonical, which side of a contradiction is correct, and whether near-name distinctions are intentional, before changing anything. - Severity-ranked findings and safe fixes: Reports findings ranked as blocking, important, or nit, then applies approved normalizations across every file without silently resolving contradictions. - Use Case: You inherit a Cucumber suite where one feature says a coupon gives 10% off and another says 15%, and steps like "I am logged in" and "the user is signed in" coexist. Run this Skill to surface every conflict and unify the suite's language. ## Quick Start Review all the .feature files in my features directory for contradictions, duplicate steps, and inconsistent terminology, then help me reconcile them.

Frequently Asked Questions about review-feature-suite

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find duplicate steps across multiple Gherkin feature files?▼

Extract every Given, When, Then, And, and But line across all files, then cluster steps by behavior rather than string similarity. Steps like "I am logged in" and "the user is signed in" are duplicates despite different wording, while differing parameter values may be intentional.

How do I check Gherkin scenarios for contradictions?▼

Compare scenarios that share the same precondition and action but assert different outcomes, such as a discount code giving 10% off in one feature and 15% in another. Report each conflict and let the team decide which outcome is correct, since it is a business decision.

Does this work with Cucumber, SpecFlow, and Behave feature files?▼

Yes, the audit operates on plain .feature files written in Gherkin, so it works with Cucumber, SpecFlow, Behave, or any framework using standard Gherkin syntax. It analyzes the files as text without executing step definitions.

When should I use a single-feature review instead of a suite audit?▼

Use a single-feature skill such as define-behavior when authoring or refining one feature file on its own. A suite-wide audit is only needed when you have several feature files and want to align language, remove duplication, or resolve contradictions across them.

Why does step phrasing consistency matter in a BDD suite?▼

Each distinct step phrasing tends to spawn its own step definition in the automation layer, so drift quietly doubles the code behind the suite. Identical phrasing for identical behavior keeps the step definition library small and reusable.