DEVOPS
Lead-Time Regression Alert for Slow Teams
Each weekday morning, checks every team's rolling 7-day lead time against its 30-day baseline and posts a Slack alert that names any team whose lead time has degraded beyond…
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday 09:00 schedule
- ActionFetch trailing-30-day MRs and deploy timesGitLab
- LogicCompute 7-day vs 30-day median lead time per team
- LogicKeep teams over the regression threshold
- OutputPost flagged-teams alert to SlackSlack
What it does
This is a watchdog for delivery speed. It compares each team's recent lead-time-for-changes to its own historical baseline and proactively flags teams that are slowing down, so the regression is caught early.
When to use it
Use it when you care less about the absolute numbers and more about catching negative trends fast — surfacing a team whose merge-to-deploy time jumped this week before it becomes a quarter-long problem.
How it works
- 1A weekday 09:00 schedule fires the check.
- 2An action queries the GitLab API for merged MRs and their deploy times over the trailing 30 days, grouped by team.
- 3A compute step calculates each team's rolling 7-day median lead time and its 30-day baseline median.
- 4A logic branch keeps only teams whose 7-day median exceeds the baseline by more than the configured percentage threshold.
- 5If any team qualifies, the output step posts a Slack message to the platform channel listing each flagged team, its current versus baseline lead time, and the percent change. If none qualify, the run ends silently.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.