DEVOPS
Triage bundle regression and open GitLab issue
When an MR bundle delta breaches budget, an agent inspects the dependency and route diffs to identify the likely cause.
How it runs
The automated pipeline, trigger to output.
- TriggerBundle-budget breach event received
- ActionFetch per-route size breakdownVercel
- ActionPull MR diff and changed depsGitLab
- LogicAgent correlates growth to likely culpritOpenAI
- OutputFile GitLab issue with cause and fixGitLab
What it does
When a preview build's bundle exceeds budget, this agent-driven workflow goes beyond flagging the number. It pulls the MR diff and the per-route size breakdown from the build, reasons about which newly added or upgraded dependency or imported module most likely caused the growth, and files a GitLab issue describing the suspected culprit with a concrete remediation suggestion (dynamic import, dependency swap, tree-shake).
When to use it
Use it when bundle regressions land often enough that manual root-cause hunting is a drag, and you want a starting hypothesis and ticket auto-created so the owning team can act quickly.
How it works
- 1A bundle-budget breach event triggers the run with the MR and deploy context.
- 2Fetch the build's per-route size breakdown from Vercel.
- 3Pull the MR diff and changed dependencies from GitLab.
- 4The agent correlates size growth with the diff to name a likely culprit and fix.
- 5File a GitLab issue with findings, suspected cause, and suggested remediation.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 3Connect OpenAIModels, embeddings, files.
- 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
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-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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.