DEVOPS
Agent-Driven Perf Budget Triage and Linear Ticket
When a preview deploy fails its performance budget, an agent investigates the diff to identify the likely cause, drafts a remediation plan.
How it runs
The automated pipeline, trigger to output.
- TriggerBudget-failure webhook receivedHTTP webhook
- ActionPull PR diff and package changesGitHub
- LogicAgent diagnoses likely regression causeOpenAI
- ActionOpen assigned Linear ticket with fix planLinear
- OutputComment summary on the PRGitHub
What it does
Turns a red performance gate into actionable work instead of just a failing check. When a preview deployment breaches its bundle or Web Vitals budget, an agent pulls the PR diff and dependency changes, reasons about what likely caused the regression, and files a Linear ticket with a prioritized fix plan assigned to the author.
When to use it
Use it when failing checks pile up but nobody knows why a route got heavier. The agent does the first-pass investigation so engineers start from a hypothesis, not a blank console.
How it works
- 1A failed-budget webhook from the gate workflow triggers the run with the offending routes.
- 2An action pulls the PR's changed files and package diff from GitHub.
- 3The agent analyzes the diff against the size delta to identify likely culprits, such as a new heavy import or an unsplit chunk.
- 4It drafts a remediation plan with specific suggestions like dynamic import or tree-shaking.
- 5It opens a Linear issue assigned to the PR author with the plan and evidence.
- 6It posts a short summary back to the PR thread on GitHub.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect OpenAIModels, embeddings, files.
- 4Connect LinearIssues, projects, cycles, triage.
- 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
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.
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.
Generate a weekly de-flake report and assign Linear cleanup tickets
On a weekly schedule, aggregates the current quarantine manifest and recent flake history, builds a prioritized report.
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-release tests from quarantine once they prove stable
Triggered by a webhook from a nightly stability runner, checks whether quarantined tests have passed enough consecutive runs, removes the stable ones from quarantine in GitHub.
Quarantine a test on demand from a PR comment command
Triggered when an engineer comments a quarantine command on a pull request, validates the test name, commits the quarantine change to that PR branch, opens a tracking issue.
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.