DEVOPS
Block PRs that add heavy dependencies past a weight budget
When a PR changes package.json or the lockfile, measures the installed and bundled weight of newly added dependencies.
How it runs
The automated pipeline, trigger to output.
- TriggerPR changes package.json or lockfileGitHub
- ActionInstall and measure added dependency weightShell
- LogicCompare added weight to dependency budget
- ActionSet pass/fail GitHub check listing packagesGitHub
- OutputNotify platform team in Microsoft TeamsMicrosoft Teams
What it does
Many bundle regressions trace back to one careless `npm install`. This gate watches dependency manifest changes specifically, computes how much weight each newly added package contributes to the client bundle, and blocks the PR when the total added weight crosses your budget. It catches the moment a 300 KB date library or duplicate framework sneaks in.
When to use it
Use it when you want a focused guard on the supply-chain side of bundle size, separate from your general size gate. It's especially valuable on teams where many contributors add dependencies without realizing the cost.
How it works
- 1A GitHub pull_request event fires only when package.json or the lockfile changed.
- 2A shell step installs the new dependency set and measures each added package's bundled contribution.
- 3A logic step sums the added weight and compares it to the per-PR dependency budget.
- 4If over budget, the flow sets a failing GitHub check listing the offending packages and their sizes.
- 5A Microsoft Teams message notifies the platform team so they can advise a lighter alternative.
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 Microsoft TeamsChannels, chats, 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
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.