DEVOPS
Comment a per-route bundle delta table on each PR
On every pull request, builds both the base and head branches, diffs the bundle size of each route.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR opened or updatedGitHub
- ActionBuild base and head branchesShell
- LogicDiff per-route bundle sizes
- OutputUpsert per-route delta table PR commentGitHub
What it does
Instead of a single pass/fail number, this gives reviewers the receipts: a table showing the byte delta for every route the PR touched. Reviewers see at a glance that, say, /checkout grew 40 KB while /home shrank, making it obvious where the weight landed and whether it's justified.
When to use it
Use it when you want bundle changes to be a normal part of code review rather than an opaque gate. It pairs well with a hard threshold gate but focuses on visibility and reviewer judgment instead of blocking.
How it works
- 1A GitHub pull_request event fires on open or update.
- 2A shell step builds the base branch and the head branch and records per-route gzipped sizes for each.
- 3A logic step joins the two manifests and computes the delta per route, sorting by largest increase.
- 4An action upserts a single sticky comment on the PR with the formatted markdown table, replacing any prior comment from this flow.
- 5The comment highlights routes whose increase exceeds the soft warning threshold.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.