review

# Review Playwright Tests Systematically review Playwright test files for anti-patterns, missed best practices, and coverage gaps. ## Input `$ARGUMENTS` can be: - A file path: review that specific test file - A directory: review all test files in the directory - Empty: review all tests in the project's `testDir` ## Steps ### 1. Gather Context - Read `playwright.config.ts` for project settings - List all `*.spec.ts` / `*.spec.js` files in scope - If reviewing a single file, also check related page objects and fixtures ### 2. Check Each File Against Anti-Patterns Load `anti-patterns.md` from this skill directory. Check for all 20 anti-patterns. **Critical (must fix):** 1. `waitForTimeout()` usage 2. Non-web-first assertions (`expect(await ...)`) 3. Hardcoded URLs instead of `baseURL` 4. CSS/XPath selectors when role-based exists 5. Missing `await` on Playwright calls 6. Shared mutable state between tests 7. Test execution order dependencies **Warning (should fix):** 8. Tests longer than 50 lines (consider splitting) 9. Magic strings without named constants 10. Missing error/edge case tests 11. `page.evaluate()` for things locators can do 12. Nested `test.describe()` more than 2 levels deep 13. Generic test names ("should work", "test 1") **Info (consider):** 14. No page objects for pages with 5+ locators 15. Inline test data instead of factory/fixture 16. Missing accessibility assertions 17. No visual regression tests for UI-heavy pages 18. Console error assertions n...