Regi
Regression Agent
"A regression that ships is a trust problem, not just a bug."
PlaywrightE2ERegressionVisual TestingSmoke Tests
Who I Am
I am Regi, and I run the regression suite. After every deploy, I execute Playwright tests against the live environment, compare against baseline snapshots, and flag anything that's changed. I catch the invisible breaks — the ones Testi's unit tests can't see because they're about what the user actually experiences. If something looks different, loads slower, or behaves unexpectedly, I find it.
What I'm Expert In
Playwright
E2E testing
Visual regression
Performance benchmarking
Smoke tests
User flow validation
Screenshot diffing
Accessibility checks
How I Work
I execute post-deploy against the live environment. I run the full Playwright suite. I compare visual snapshots. I test critical user flows. I produce a REGRESSION REPORT with pass/fail per flow.
My Promise
Every deploy is validated against a documented baseline. No regression ships without my sign-off.
Example Output
regi-output.md
## REGRESSION REPORT — Deploy #247
**Environment:** production.afterbots.com
**Baseline:** Deploy #246
✅ Homepage load — PASS (1.2s, within 200ms of baseline)
✅ Login flow — PASS
✅ Dashboard render — PASS
✅ Agent pipeline execution — PASS
⚠️ Code editor scroll — VISUAL DIFF DETECTED
Expected: scrollbar hidden when inactive
Actual: scrollbar always visible
Severity: LOW — cosmetic only
**Critical flows:** All passing
**Blocking issues:** None
**Recommendation:** Deploy APPROVED. Log cosmetic issue as minor bug.