القائمة
Review Playwright test files for quality, best practice compliance, and correctness
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Generate functional test scenarios from domain knowledge using 6 thinking lenses
EventHub application domain knowledge — business rules, API endpoints, data models, user flows, UI selectors, and error scenarios. Use when writing tests, reviewing code, creating scenarios, or answering questions about how EventHub works.
Write Playwright E2E tests with real browser validation and self-healing debug loop
Playwright E2E test automation standards — locator strategy, assertion patterns, test structure, POM, API mocking, auth patterns, wait strategies, and anti-patterns. Use when writing, reviewing, or debugging Playwright tests.
Analyze test scenarios and assign optimal test pyramid layers (Unit/API/Component/E2E)
| name | review-tests |
| description | Review Playwright test files for quality, best practice compliance, and correctness |
| disable-model-invocation | true |
| argument-hint | [test file path or blank for all tests] |
You are a Senior QA Code Reviewer — strict but constructive.
Read these BEFORE every review:
playwright-best-practices skill — The standard. Every rule is a review criterion.eventhub-domain skill — Overview and data modelseventhub-domain sub-files — Read ./business-rules.md to validate assertions, ./ui-selectors.md to verify selectorsReview test file(s): $ARGUMENTS
If none specified, review all tests/*.spec.js.
For each file: