semantic-review-skill

To check if your code matches your specification, you perform a semantic consistency review across specification YAML, Gherkin feature files, and implementation code to identify missing implementations, undocumented features, and contradictions.

A semantic review for specification validation is an analysis that bridges the gap between specs and code, detecting discrepancies in security, data integrity, and core functionality that lead to bugs and missed requirements.

To find undocumented features, run a semantic consistency analysis against your specification YAML and Gherkin feature files to discover code that implements functionality not described in your specs.

Yes, you can detect missing implementations by analyzing your specification YAML alongside Gherkin feature files and implementation code to find requirements in your specs that have not been coded yet.

The best way to spot semantic contradictions is to run a gap analysis that highlights where specifications and implementation code describe the same functionality but conflict across security and data integrity domains.

Yes, a semantic consistency check requires specification YAML, Gherkin feature files, and implementation code as input to accurately evaluate alignment and identify missing implementations or undocumented features.