DEVOPS
Triage a failed preview smoke run and file a structured bug
When a preview smoke check fails, an agent inspects the browser trace and console errors, determines the likely root cause.
How it runs
The automated pipeline, trigger to output.
- TriggerFailed preview smoke run received
- ActionAgent reviews browser trace and console errors for root causeBrowserbase
- ActionSearch Linear for a matching open issueLinear
- LogicDecide comment on existing vs create new
- ActionFile Linear bug with repro steps and PR linkLinear
- OutputPost issue link back to the GitHub PRGitHub
What it does
When a preview smoke check fails this workflow doesn't just alert - an agent investigates. It reads the browser trace, console errors, and the failing step, reasons about the likely cause, checks for an existing matching issue, and files a clean Linear bug with repro steps linked back to the PR.
When to use it
Use it when smoke failures pile up faster than engineers can triage them, and you want each failure turned into an actionable, deduplicated ticket instead of a noisy Slack ping.
How it works
- 1A failed smoke run (from the gate workflow) triggers this flow with the trace, console log, and preview URL.
- 2The agent reviews the trace and console errors to identify the failing path and a probable root cause.
- 3It searches Linear for an open issue matching the same path and signature.
- 4A logic branch decides: comment on the existing issue, or create a new one.
- 5For a new bug, it files a Linear issue with reproduction steps, severity, and the PR link.
- 6It posts the issue link back to the PR thread so reviewers see the triage outcome.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect BrowserbaseHeadless browsers, sessions, replays.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect OpenAIModels, embeddings, files.
- 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.