DEVOPS
PR-comment visual review with one-click baseline approval
On each pull request preview, renders the changed pages, posts an annotated visual review comment on the PR.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR opened or updated with previewGitHub
- ActionRender changed routes in headless browserBrowserbase
- ActionPost diff montage as PR review commentGitHub
- LogicBranch: maintainer replied /approve-baseline?
- OutputPromote screenshots to baseline in S3AWS S3
What it does
This workflow keeps the visual baseline honest by putting a human in the loop. When a PR gets a preview deploy, it renders the affected pages, builds a diff montage, and posts it as a structured GitHub PR comment. Intentional UI changes are approved with a single comment command, which promotes the new screenshots to the baseline so the next preview compares cleanly.
When to use it
Use it when your visual diffs are noisy because the design genuinely changes often. Instead of a hard auto-block, this gives reviewers an inline visual review next to the code, and a clean way to bless intended changes without editing baseline files by hand.
How it works
- 1A GitHub pull_request event with an attached preview deployment triggers the run.
- 2The workflow reads the PR's changed files to decide which routes to render.
- 3A headless browser captures those routes and diffs them against the baseline.
- 4A diff montage is posted as a PR comment summarizing changed pixels per page.
- 5A branch listens for an `/approve-baseline` reply from a maintainer.
- 6On approval, the new screenshots are written to object storage as the updated baseline.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect AWS S3Buckets, objects, signed URLs.
- 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.