review-tests

Review pytest-playwright test files for best practice compliance and correctness.

1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/marcocelone/demo-python-ai-agent-project --skill review-tests-marcocelone
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-tests
Source: https://github.com/marcocelone/demo-python-ai-agent-project/tree/main/.claude/skills/review-tests
Command: npx skills add https://github.com/marcocelone/demo-python-ai-agent-project --skill review-tests-marcocelone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? End-to-end test suites often accumulate quality issues like hardcoded waits, misplaced assertions, and selectors that no longer match the frontend source. This Skill performs a structured code review of pytest-playwright test files against a defined best-practices checklist and domain knowledge, producing actionable findings with exact line numbers. ## Core Features & Use Cases - Rule-Based Review: Checks every line of test code against the playwright-best-practices skill, flagging violations as CRITICAL, IMPORTANT, or SUGGESTION. - Selector Verification: Cross-references data-testid selectors in tests against the actual frontend source code to confirm they exist. - Domain Assertion Validation: Validates test assertions against business rules and UI selector documentation from the eventhub-domain skill. - Use Case: After writing a new booking management test file, run the review to catch page.wait_for_timeout() calls, assertions hidden inside Page Object methods, and stale selectors before merging. ## Quick Start Ask the reviewer to review tests/test_booking_management.py for best practice violations and selector correctness.

Frequently Asked Questions about review-tests

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

FAQPage Schema
How do I review pytest-playwright tests for best practices?▼

Invoke the review with a test file path, or leave it blank to review all files matching tests/test_*.py. The reviewer reads the best practices checklist, compares every line, and reports issues with severity tags, line numbers, and fixes.

What issues does a Playwright test code review flag?▼

The review flags time.sleep() and page.wait_for_timeout() usage as CRITICAL, and assertions inside Page Object Model methods as IMPORTANT. It also checks selectors against frontend source and validates assertions against domain business rules.

Can the reviewer verify data-testid selectors exist in the frontend?▼

Yes. The review process reads the frontend app and components directories to confirm each selector used in tests actually exists in the source code, rather than assuming selectors are valid.

What output format does the test review produce?▼

Each file gets a What's Good section, an Issues Found list tagged CRITICAL, IMPORTANT, or SUGGESTION with line numbers and fixes, a score out of 10, and recommended fixes in priority order.

When should I not use automated test review?▼

Automated review checks rule compliance and selector correctness but cannot judge whether test scenarios cover real user risk. Use it alongside manual test design review for coverage and business logic decisions.