DEVOPS
Vercel Preview Agent Review Gate
Spins up an AI reviewer that reads the PR diff and exercises the matching Vercel preview in a browser.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deployment succeededVercel
- ActionFetch PR diff and description for contextGitHub
- ActionProbe changed surfaces in the preview browserBrowserbase
- LogicReason to a pass/block verdict with rationale
- OutputPost reasoned checklist and set agent-review statusGitHub
What it does
Adds an agentic QA reviewer to the preview gate. When a preview is ready, the agent pulls the PR diff for context, opens the preview in a browser to verify the changed surfaces actually behave, and reasons about whether the change is merge-safe. It writes a structured checklist (what it tested, what passed, what concerned it) to the PR and gates merge accordingly.
When to use it
Use it when checks need judgment a fixed script can't encode, like confirming a UI change matches its intent or that an edge case from the diff was handled. Pairs well with deterministic gates as a second, smarter pass.
How it works
- 1Vercel sends a deployment-succeeded webhook with the preview URL and commit SHA.
- 2The agent fetches the PR diff and description from GitHub to understand what changed.
- 3Using Browserbase, the agent navigates the preview and probes the surfaces the diff touched.
- 4The agent reasons over its observations to a pass or block verdict with rationale.
- 5GitHub receives a `agent-review` commit status and a written checklist comment explaining the decision.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect BrowserbaseHeadless browsers, sessions, replays.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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.
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.
Open a Zoom war-room from a Datadog multi-alert storm
When a Datadog monitor crosses a critical threshold, this workflow dedupes against active incidents, and only for a genuinely new outage it creates a Zoom bridge.
Auto-spin a Zoom war-room when PagerDuty hits SEV-1
When a PagerDuty incident escalates to a critical severity, this workflow creates a dedicated Zoom meeting and posts the bridge link to the incident's Slack channel so responders…
Spin up a war-room on demand from a Slack slash command
When an engineer runs a Slack command, this workflow creates a Zoom bridge, opens a tracking Sentry-linked incident, files a Linear issue for follow-up.
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.