DEVOPS
Vercel Bundle-Size Budget Gate on Pull Requests
Compares the bundle size of a Vercel preview deploy against the production baseline on every PR and posts a pass/fail GitHub status check that blocks merges exceeding…
How it runs
The automated pipeline, trigger to output.
- TriggerVercel preview deploy ready webhookVercel
- ActionFetch per-route bundle sizes from build outputVercel
- ActionLoad production baseline sizesPostgres
- LogicCompare route deltas against byte budget
- OutputPost pass/fail GitHub commit status on the PRGitHub
What it does
Enforces a hard bundle-size budget on every pull request. When a preview deploy finishes, it pulls the build's route-level JavaScript sizes, diffs them against the current production baseline, and writes a GitHub commit status that blocks the merge if any route grows past its allowed delta.
When to use it
Use it when you want bundle bloat to fail CI the same way a broken test does, rather than being noticed weeks later. Ideal for teams shipping a Next.js or similar app on Vercel where first-load JS directly affects user experience.
How it works
- 1A Vercel deployment-ready webhook fires when a preview build for a PR completes.
- 2The flow fetches the build output and per-route bundle sizes from the Vercel API.
- 3It reads the stored production baseline sizes from Postgres.
- 4A budget check compares each route delta against its configured byte threshold.
- 5If any route exceeds budget the flow posts a failing GitHub commit status with the offending routes; otherwise it posts success. The status appears directly on the PR as a required check.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.