PR QA Copilot: route-aware Playwright reports for Next.js previews

[ACHultman]

I maintain PR QA Copilot, an open-source GitHub Action for checking Next.js pull-request previews. Sharing a working example here for feedback.

It finds a successful GitHub deployment for the PR's head commit, opens the preview with Playwright, and checks configured paths plus static Next.js routes changed by the diff. It records uncaught page errors, console errors, failed same-origin requests, and same-origin HTTP 4xx/5xx responses.

The result is one updated PR comment. Screenshots, journey results, and an HTML gallery are uploaded separately as a GitHub Actions artifact.

This report from my own site covers four routes and a three-step homepage-to-about journey against a protected Vercel preview. This is my own installation, not a customer case study. The report uses runtime checks and screenshots; visual diffs were disabled.

A few boundaries:

• Browser journeys are explicitly configured in JSON; the action does not invent them.
• Automatic route selection is limited to static routes. Other paths need configuration.
• It starts in reporting mode so teams can tune noisy checks before making them a merge gate.
• The browser checks do not need an OpenAI API key.

Installation and configuration.

For teams reviewing several Next.js projects, would this PR-level report remove a review step, or mostly duplicate your existing Playwright checks? I would welcome examples of preview failures your current CI misses. Please keep repository credentials and private customer details out of the discussion.