DEVOPS
Performance budget gate blocking previews on Lighthouse regression
Runs a Lighthouse audit against each Vercel preview, compares core web vitals to production, and blocks promotion plus warns Slack when LCP, CLS, or the performance score regress…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deploy readyVercel
- ActionRun headless Lighthouse audit on previewShell
- LogicBranch: web vitals regressed past budget?
- ActionSet failing GitHub commit statusGitHub
- OutputPost metric deltas to SlackSlack
What it does
This workflow enforces a performance budget on every preview before it can be promoted. It runs a headless Lighthouse audit against the preview URL, extracts core web vitals and the performance score, and compares them to the production baseline. Builds that regress beyond your tolerances are blocked, with the specific metric deltas reported.
When to use it
Use it when frontend performance keeps quietly degrading and nobody notices until users complain. It is ideal for marketing or storefront pages where a slow LCP directly costs conversions, and gives teams a hard, automated brake on shipping a heavier bundle.
How it works
- 1A Vercel preview-ready webhook triggers the run.
- 2A shell step runs Lighthouse headlessly against the preview URL and emits JSON.
- 3The metrics are compared against the stored production baseline for LCP, CLS, TBT, and score.
- 4A branch checks whether any metric regressed past its budget.
- 5If it did, a failing GitHub commit status blocks promotion.
- 6Slack gets a summary table of metric deltas and the verdict.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, 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.