e2e-rebase_skill

Overview

This skill automates rebasing E2E test snapshots by parsing failing Playwright results posted in PR comments and updating snapshots for the affected tests. It runs targeted commands to update snapshots, verifies the updates, shows diffs, and pushes the changes back to the PR when everything looks correct. The workflow ensures snapshots match the built app version and prevents flaky changes from being committed.

How this skill works

The skill reads the current PR number and scans PR comments for the Playwright test results block. It extracts failed test filenames from either the "Failed Tests" list or the "Update Snapshot Commands" block. For each failed test it builds the app if necessary, updates snapshots via Playwright with the update flag, reruns the test to verify stability, shows git diffs of snapshot files, and if everything is reasonable, commits and pushes the snapshot updates to the PR.

When to use it

• A PR has Playwright results posted and snapshots failed.
• You changed UI or behavior that should intentionally update snapshots.
• You need to rebase snapshots for only the tests that failed.
• You want to avoid running the entire E2E suite locally.
• You want automated, targeted snapshot updates tied to the PR.

Best practices

• Always run the build step first if any non-e2e files changed; snapshots must match the built binary.
• Inspect git diffs of snapshots to confirm changes align with the PR intent.
• Re-run updated tests without --update-snapshots to ensure updates are stable.
• Avoid committing snapshot noise; reject updates that look unrelated or flaky.
• Run these steps on the same environment that produced the original Playwright output.

Example use cases

• A PR changes component styling which causes a few E2E snapshot failures — update only those snapshots and push.
• CI posts Playwright results in a PR; use this skill to parse the comment and rebase the listed snapshots.
• A contributor updates text content and snapshots need rebasing for specific spec files.
• You want to quickly verify snapshot updates locally before committing them to the PR.