DEVOPS
Lead-Time Bottleneck Finder for Open Pull Requests
Daily, scans open GitHub pull requests, flags ones stuck in review or awaiting deploy beyond your lead-time target.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily morning schedule
- ActionList open PRs with review state and timestampsGitHub
- LogicFlag PRs over lead-time threshold, dedupe
- ActionCreate or update Linear task per stuck PRLinear
- OutputPost new-bottleneck summary to SlackSlack
What it does
Instead of measuring lead time after the fact, this workflow attacks it while it's still accruing. Each day it scans open pull requests, calculates how long each has been waiting since first review-ready, and flags any exceeding your lead-time target. For each laggard it opens a Linear task assigned to the right owner, so review and deploy bottlenecks get cleared before they hurt your DORA numbers.
When to use it
Use it when lead time for changes is your weak DORA metric and you want a proactive nudge on stuck PRs rather than a postmortem. Ideal for teams that triage work in Linear.
How it works
- 1A daily schedule fires each morning.
- 2The flow lists all open PRs across tracked repos with their review state and timestamps.
- 3A logic step computes age-since-ready per PR and keeps those over the lead-time threshold, deduping ones already flagged.
- 4For each flagged PR it creates or updates a Linear task tagged with the PR link and stuck reason.
- 5The final step posts a short summary of new bottlenecks to the team's Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.