Menu
Rebase E2E test snapshots based on failed tests from the PR comments.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Commit any uncommitted changes, run lint checks, fix any issues, and push the current branch.
Root-cause flaky or failing E2E tests from a specific CI run by downloading and analyzing the Playwright HTML report (traces, screenshots, errors). Use this when given a GitHub Actions run URL and asked to investigate failures. Diagnose from report artifacts first, then rebuild and rerun the affected E2E tests locally after making fixes.
Fix failing CI checks and GitHub Actions on a Pull Request.
Read all unresolved GitHub PR comments from trusted authors and address or resolve them appropriately.
Automatically gather flaky E2E tests from recent CI runs on the main branch and from recent PRs by wwwillchen/keppo-bot/dyad-assistant, then deflake them.
Promote the latest pre-release to a stable release by creating a release branch, bumping the version, and pushing.
| name | dyad:e2e-rebase |
| description | Rebase E2E test snapshots based on failed tests from the PR comments. |
Rebase E2E test snapshots based on failed tests from the PR comments.
Get the current PR number using gh pr view --json number --jq '.number'
Fetch PR comments and look for the Playwright test results comment. Parse out the failed test filenames from either:
- \filename.spec.ts`)npm run e2e e2e-tests/filename.spec.ts)If no failed tests are found in the PR comments, inform the user and stop.
Build the application binary:
npm run build
IMPORTANT: E2E tests run against the built binary. If any application code (anything outside of e2e-tests/) has changed, you MUST run this build step before running E2E tests, otherwise you'll be testing the old version.
For each failed test file, run the e2e test with snapshot update:
PLAYWRIGHT_HTML_OPEN=never npm run e2e e2e-tests/<testFilename>.spec.ts -- --update-snapshots
After updating snapshots, re-run the same tests WITHOUT --update-snapshots to verify they pass consistently:
PLAYWRIGHT_HTML_OPEN=never npm run e2e e2e-tests/<testFilename>.spec.ts
If any test fails on this verification run, inform the user that the snapshots may be flaky and stop.
Show the user which snapshots were updated using git diff on the snapshot files.
Review the snapshot changes to ensure they look reasonable and are consistent with the PR's purpose. Consider:
If the snapshots look reasonable, commit and push the changes:
git add e2e-tests/snapshots/
git commit -m "Update E2E snapshots"
git push
Inform the user that the snapshots have been updated and pushed to the PR.