pw-review

Reviews Playwright test files for anti-patterns, scores quality, and suggests fixes.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill pw-review-rohithdgrr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pw-review
Source: https://github.com/Rohithdgrr/REEK-uninstaller/tree/main/.opencode/skills/pw-review
Command: npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill pw-review-rohithdgrr

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Playwright test suites often accumulate flaky patterns like hardcoded waits, brittle CSS selectors, and missing awaits that cause intermittent CI failures. This Skill systematically audits test files against 20 known anti-patterns and produces actionable, scored review reports. ## Core Features & Use Cases - Anti-Pattern Detection: Checks each test file against 20 categorized anti-patterns (critical, warning, info), including waitForTimeout usage, non-web-first assertions, and shared mutable state. - Quality Scoring: Rates every file on a 1-10 scale with line-specific findings and concrete corrected code suggestions. - Project-Wide Audits: Reviews entire test suites with parallel sub-agents, aggregating results into a summary table with coverage gap analysis. - Use Case: Before merging a large test suite, run a review to catch flaky patterns like waitForTimeout(2000) and get the exact expect(locator).toBeVisible() replacement, then apply all fixes automatically. ## Quick Start Ask the AI to review the Playwright tests in your tests directory for quality issues and anti-patterns.

Frequently Asked Questions about pw-review

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

FAQPage Schema
How do I review Playwright tests for best practices?▼

Point the review at a spec file, directory, or the project's testDir. It checks each file against 20 anti-patterns, scores quality from 1-10, and reports line-specific issues with corrected code you can apply automatically.

What Playwright anti-patterns cause flaky tests?▼

The most critical are waitForTimeout calls, non-web-first assertions like expect(await ...), missing awaits on Playwright calls, shared mutable state between tests, and test execution order dependencies. These are flagged as must-fix critical issues.

Can I review an entire Playwright test suite at once?▼

Yes. Pass a directory or leave the argument empty to review all tests in the project's testDir. Large suites are reviewed with parallel sub-agents (up to 5 concurrent) and aggregated into a summary table with average scores.

Does the Playwright test review apply fixes automatically?▼

It provides corrected code for every critical issue and asks for confirmation before applying changes. If you approve, all fixes are applied to the test files using edit operations.

Why use role-based locators instead of CSS selectors in Playwright?▼

Role-based locators like getByRole reflect how users and assistive technology perceive the page, making tests resilient to styling changes. The review flags CSS and XPath selectors as critical issues when a role-based alternative exists.