DEVOPS
Block PR merges when the Vercel bundle exceeds budget
On every pull request, builds the app, compares total client bundle size against a baseline budget.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR opened or updatedGitHub
- ActionBuild app and measure gzipped bundleShell
- LogicCompare bundle size to baseline budget
- ActionSet pass/fail GitHub commit status checkGitHub
- OutputPost result summary to SlackSlack
What it does
This gate stops bundle bloat from reaching production. When a pull request opens or updates, it builds the branch, measures the gzipped client bundle, and compares it against the budget you set (for example, no more than a 5% increase over the current main baseline). If the bundle grows past that line, the PR's required status check turns red and the merge button locks. A passing build flips the check green automatically.
When to use it
Use it on any Next.js or front-end repo on Vercel where page weight matters for performance and Core Web Vitals. It's the cleanest way to make bundle size a hard merge requirement rather than a thing people notice after shipping.
How it works
- 1A GitHub pull_request event fires when a PR opens or gets new commits.
- 2A shell step runs the production build and extracts the total gzipped bundle size from the build manifest.
- 3A logic step compares the new size against the stored baseline and computes the percent delta.
- 4If the delta exceeds the threshold, the flow posts a failing GitHub commit status; otherwise it posts a passing one.
- 5A Slack message summarizes the result with the exact byte delta and a link to the PR.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.