DEVOPS
Visual-regression gate on Vercel previews with GitHub status
Captures screenshots of key pages on each Vercel preview, diffs them against approved baselines.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment readyVercel
- ActionScreenshot critical routes in browserBrowserbase
- ActionDiff against baselines in S3AWS S3
- LogicAny route over diff threshold?
- OutputWrite pass/fail commit status to PRGitHub
What it does
This workflow adds an automated visual-regression check to your Vercel preview pipeline. For every preview deploy it loads a list of critical routes in a real browser, screenshots them, and compares each against a stored baseline image. The pixel-diff result becomes a GitHub commit status, so an unexpected visual change keeps the PR's merge button red until a human signs off.
When to use it
Use it when CSS or component refactors keep slipping visual breakage into production and you want a required check that catches layout shifts before merge.
How it works
- 1A Vercel deployment-ready webhook provides the preview URL and the commit SHA.
- 2A Browserbase step navigates to each configured route and captures full-page screenshots.
- 3The screenshots are diffed against baselines stored in S3; a percentage-changed value is computed per route.
- 4A logic branch checks whether any route exceeds the allowed diff threshold.
- 5An action posts a GitHub commit status (success or failure) against the PR's SHA, with the diff summary in the description.
- 6On failure, a Slack note links the diff images so a reviewer can approve or reject.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect AWS S3Buckets, objects, signed URLs.
- 4Connect GitHubRepos, issues, pull requests, actions.
- 5Connect SlackChannels, DMs, threads, mentions.
- 6Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 7Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 8Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
Hugging Face Spaces idle-runtime sweep with auto-pause
On a schedule, scans all Hugging Face Spaces for ones running idle past a threshold, pauses them to stop billing, and posts a Slack summary with the estimated monthly savings.
Slack-approved pause for idle Hugging Face Spaces
On a daily scan it finds idle paid Spaces and posts an interactive Slack approval; on approve it pauses the Space and logs the decision to a GitHub issue audit trail.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
Block costly Hugging Face Space hardware upgrades in PR review
When a pull request changes a Space's hardware config, it estimates the new monthly cost and posts a GitHub PR comment that flags upgrades crossing a budget ceiling.
Auto-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.