ENGINEERING
Loom Bug Triage with Severity Routing to Linear
Transcribes a shared Loom bug video, classifies its severity and affected area, then creates a Linear issue routed to the right team with priority set.
How it runs
The automated pipeline, trigger to output.
- TriggerNew bug Loom sharedLoom
- ActionFetch transcript and recording detailsLoom
- ActionExtract repro + classify severity and areaOpenAI
- LogicMap severity/area to team + priority
- ActionCreate routed Linear issueLinear
- OutputAlert on-call in Slack if blockerSlack
What it does
Triages bug-report Looms and routes them into Linear with the correct team, priority, and labels already set. It reads the transcript, judges severity (blocker through minor) and the affected product area, files the issue on the owning team's board, and pings on-call in Slack when something is a blocker.
When to use it
Use it when bug Looms pile up in one inbox and someone has to manually decide who owns each one and how urgent it is. This gives you consistent severity grading and gets criticals in front of the right team in seconds instead of hours.
How it works
- 1A shared Loom video triggers the flow.
- 2Loom returns the transcript and recording details.
- 3An OpenAI step writes the repro steps and assigns severity plus an affected-area label from your taxonomy.
- 4A logic branch maps severity and area to the owning Linear team and priority.
- 5A Linear action creates the issue with priority, labels, and the Loom link.
- 6If severity is blocker or urgent, a Slack message alerts the on-call channel.
Set it up
What you configure once, before turning it on.
- 1Connect LoomVideo transcripts, libraries.
- 2Connect OpenAIModels, embeddings, files.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 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 Engineering workflows
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
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.