DEVOPS
Agent triage of failed Lighthouse budgets with PR fix suggestions
When a Vercel preview fails its Lighthouse budget, an agent inspects the report and changed files, identifies the likely cause.
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview audited, budget failedVercel
- LogicDetect failed Lighthouse budget
- ActionFetch report and changed files from GitHubGitHub
- ActionAgent diagnoses cause and drafts fixesOpenAI
- OutputPost remediation comment on the PRGitHub
What it does
A raw failing Lighthouse score tells you that the build is slow but not why. This workflow hands the failed report and the PR's changed files to an agent that correlates the regression to likely culprits, such as an unoptimized image, a render-blocking script, or a new dependency, and writes an actionable GitHub PR comment with specific fixes, then holds promotion.
When to use it
Use this when your team loses time deciphering Lighthouse output and you want first-pass triage done automatically. It turns a red gate into a ready-to-action checklist on the PR, shortening the fix loop.
How it works
- 1A Vercel preview deploy is audited and a logic step detects a failed budget.
- 2An action pulls the Lighthouse report and the PR's changed files from GitHub.
- 3The agent analyzes the diagnostics against the diff to pinpoint probable causes.
- 4The agent drafts prioritized remediation steps tied to specific files and metrics.
- 5A GitHub PR comment is posted with the findings and the deployment is held from promotion.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect GitHubRepos, issues, pull requests, actions.
- 4Connect OpenAIModels, embeddings, files.
- 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.