DEVOPS
Cloudflare Cold-Start Regression Triage Agent into Linear
On a confirmed cold-start regression, an agent gathers the suspect deploy tag's diff and recent latency data, writes a root-cause hypothesis.
How it runs
The automated pipeline, trigger to output.
- TriggerConfirmed regression webhook with tagHTTP webhook
- ActionFetch suspect tag diff and commitsGitHub
- ActionPull matching latency windowDatadog
- LogicSynthesize root-cause hypothesis
- OutputFile prioritized Linear issueLinear
What it does
When a cold-start regression is confirmed for a Cloudflare Worker, this agent-driven workflow collects the suspect deploy tag's GitHub diff and the surrounding latency measurements, reasons about the most likely cause (new heavy import, larger bundle, added top-level work), drafts a root-cause hypothesis, and opens a Linear issue routed to the responsible team with the evidence attached.
When to use it
Use it when regressions are caught but triage is the bottleneck: you want the boring evidence-gathering and first-pass diagnosis done automatically so an engineer opens a ticket that already explains what changed and where to look.
How it works
- 1A confirmed-regression webhook fires with the suspect deploy tag.
- 2The agent fetches the tag's diff and commit metadata from GitHub.
- 3It pulls the matching cold-start latency window from Datadog for evidence.
- 4The agent synthesizes a root-cause hypothesis and suggested priority.
- 5It files a Linear issue with the hypothesis, diff links, and latency evidence, assigned to the owning team.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect DatadogMetrics, traces, log search.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect HTTP webhookTrigger any URL on agent actions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More DevOps workflows
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.
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…
Page on-call when a Hugging Face Space build is stuck or errored
Polls Hugging Face Space runtime status on a schedule and opens a PagerDuty incident when a Space sits in a build or error state past a deadline, with a Slack heads-up.
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.
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.
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.