DEVOPS
Weekly build-slowdown investigation with agentic bisect
Weekly, an agent identifies the project with the worst build-minute regression, walks the recent commit and dependency changes from GitHub to hypothesize the cause.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule triggers the agent
- ActionFind worst-regressing project and slowdown window in VercelVercel
- ActionRead commits, PRs, and lockfile diffs from GitHubGitHub
- LogicReason over evidence to rank likely causes
- OutputPost root-cause brief to SlackSlack
What it does
Once a week, this agent finds the Vercel project whose build minutes regressed most, then investigates why. It pulls the deployment history from Vercel to locate the commit range where the slowdown began, reads the GitHub commits and lockfile diffs in that window, and reasons about likely culprits — a heavy new dependency, a slow build script, an exploding bundle. It writes a plain-language root-cause brief with a recommended fix.
When to use it
Use it when you keep seeing build-time alerts but nobody has time to manually bisect which change caused them. This does the detective work and hands engineering a starting hypothesis instead of a raw number.
How it works
- 1A weekly schedule triggers the agent.
- 2It queries Vercel for build durations and picks the worst-regressing project, pinpointing the deploy where the climb started.
- 3It reads the GitHub commits, PRs, and lockfile changes across that build range.
- 4It reasons over the evidence to rank candidate causes and draft a remediation suggestion.
- 5It posts the root-cause brief to Slack for the owning team to action.
Set it up
What you configure once, before turning it on.
- 1Connect VercelDeploys, runtime logs, analytics.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.