AI AGENTS
Linear Bug Triage to Sentry-Backed Repro MR
When a Linear issue is labeled 'needs-repro', an agent pulls the linked Sentry event, reproduces it, writes a failing test, opens a GitLab MR.
How it runs
The automated pipeline, trigger to output.
- TriggerLinear issue labeled needs-reproLinear
- ActionRead Linear issue and linked Sentry IDLinear
- ActionFetch Sentry event payload and traceSentry
- ActionReproduce and write failing test in shellShell
- LogicBranch on repro success or failure
- OutputOpen GitLab MR and comment result on LinearGitLab
What it does
Bridges product triage and engineering. When someone labels a Linear issue `needs-repro`, the agent reads the linked Sentry event, reproduces the failure in a shell sandbox, writes a failing test, opens a GitLab MR with the repro, and posts the outcome and MR link back on the Linear issue so triagers see whether the bug is confirmed.
When to use it
Use it when bug intake starts in Linear but reproduction and test scaffolding should be automated before an engineer commits time.
How it works
- 1A Linear webhook fires when an issue gains the `needs-repro` label.
- 2The agent reads the Linear issue and extracts the linked Sentry issue ID.
- 3It fetches the Sentry event payload and stack trace.
- 4The agent reproduces the failure in a shell sandbox and writes a failing test.
- 5Logic gate: branch on whether the repro succeeded.
- 6On success it opens a GitLab MR and comments the link on Linear; on failure it comments the diagnostic notes instead.
Set it up
What you configure once, before turning it on.
- 1Connect LinearIssues, projects, cycles, triage.
- 2Connect SentryErrors, performance, releases.
- 3Connect ShellRun sandboxed commands inside the workspace.
- 4Connect GitLabRepos, MRs, pipelines, registry.
- 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 AI Agents workflows
Custom Metrics Cardinality Spike Pager
A webhook from a Datadog monitor fires when custom-metric cardinality jumps; an agent pinpoints the offending metric and tag, estimates the added cost.
Sentry-to-Confluence Runbook Updater
When a Sentry issue is resolved, the agent finds the matching Confluence runbook page and proposes an inline update with the verified fix.
Stale Doc-PR Chaser for Runbook Gaps
On a daily schedule the agent finds runbook doc PRs that were opened from resolved incidents but never reviewed, summarizes what each one fixes.
Resolved Incident to Public Troubleshooting Doc
For customer-facing errors resolved in Sentry, the agent drafts a sanitized troubleshooting entry and opens a PR to your ReadMe documentation.
On-Call Runbook Gap Closer: Resolved Sentry Issues to Doc PRs
An agent reads each newly resolved Sentry issue, compares the actual fix against your existing runbook, and opens a GitHub PR adding the missing remediation steps.
Weekly On-Call Doc-Gap Digest
Each week the agent reviews every Sentry issue resolved in the last 7 days, ranks the ones whose runbook coverage is missing or thin.
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.