원클릭으로
lint-gherkin
// Run Gherkin linting on all feature files in the frontend directory. Use when validating Gherkin syntax, checking feature file quality, or verifying formatting compliance.
// Run Gherkin linting on all feature files in the frontend directory. Use when validating Gherkin syntax, checking feature file quality, or verifying formatting compliance.
Investigate and fix a failing Cypress test from a GitHub issue. Reads the issue for scenario details, traces the failure through step definitions, analyzes root cause, implements a fix, and verifies it locally before committing.
Create a GitHub issue on kiali/kiali for a confirmed Cypress test failure. Use after identifying a failing test (from Jenkins nightly or local run) to file a structured bug report via gh CLI.
Analyze Jenkins nightly CI failure output to identify failing Cypress/Gherkin tests, map them to feature files, classify each failure (flake / ui-bug / test-bug), and produce a triage summary ready to hand off to regression-report.
| name | lint-gherkin |
| description | Run Gherkin linting on all feature files in the frontend directory. Use when validating Gherkin syntax, checking feature file quality, or verifying formatting compliance. |
| disable-model-invocation | false |
| allowed-tools | Bash(yarn *) |
Run Gherkin linting in the frontend directory:
cd frontend && yarn lint:gherkin
Run from the Kiali repository root (the directory that contains frontend/).
The linting tool will validate all .feature files under cypress/integration/featureFiles/ and report any syntax or formatting issues.
What it checks:
If errors are found, they will be displayed with line numbers and specific rule violations.