Skip to main content

/review-test

What it does

/review-test runs the Reviewer agent in isolation. It checks a Playwright test file — and any page-object or helper files that were touched alongside it — against the project rulebook (tests/agents/rules/playwright-rules.md).

The Reviewer produces a structured PASS / FAIL verdict. For every finding it reports:

  • The file path and line number.
  • The specific rule that was violated.
  • The severity: critical, major, or minor.

A PASS means the test meets all project standards and is ready to commit. A FAIL means you should fix the findings (or rerun /generate-test to let the Generator revise) before committing.

The Reviewer does not modify any code. It only reports.

When to use it

Use /review-test after running /generate-test on its own — or any time you have edited a test file by hand and want to check it against the rulebook before committing.

You can also run it with no path argument to review the latest commit's diff. This is useful as a final sanity-check after staging your changes.

How to run it

Review a specific file:

/review-test tests/e2e/project/team/add-key-member.spec.ts

Review the latest commit's diff (no path needed):

/review-test

Example

Input:

tests/e2e/project/team/add-key-member.spec.ts (plus any POM files the Generator modified).

What you get back:

VERDICT: PASS

No rule violations found. The test is ready to commit.

Or, if findings exist:

VERDICT: FAIL

tests/e2e/project/team/add-key-member.spec.ts:42
Rule: No hard-coded text assertions — use data references
Severity: critical
Finding: 'Account Manager' is hard-coded. Reference {{team.accountManager.name}} from tests/data/ instead.

tests/e2e/project/team/add-key-member.spec.ts:58
Rule: Assertions must use the page-object assertion helpers
Severity: major
Finding: Direct .toBeVisible() call. Use teamPage.expectKeyMemberRow() instead.

Notes

  • No path = latest commit's diff. Run /review-test with no argument to review everything that changed in the most recent commit — a convenient final check before pushing.
  • The Reviewer does not modify code. It is a read-only quality gate. If the verdict is FAIL, fix the issues (manually or by re-running /generate-test) and then re-run /review-test.
  • Touched POM and helper files are included. If the Generator also modified a page-object file, the Reviewer checks those changes too — not just the .spec.ts.