ENGINEERING
Match Sentry spikes to open GitHub issues before filing in Linear
On a Sentry spike, searches open GitHub issues for a matching error signature first; if a tracking issue already exists it links and comments there, otherwise it opens…
How it runs
The automated pipeline, trigger to output.
- TriggerSentry spike alertSentry
- ActionSearch open GitHub issues by error signatureGitHub
- LogicBranch: GitHub match vs. no match
- ActionComment spike data on matched GitHub issueGitHub
- ActionResolve owning team from CODEOWNERSGitHub
- OutputCreate/update deduplicated Linear bugLinear
What it does
Prevents the Sentry-to-Linear pipeline from duplicating work that's already tracked in GitHub Issues. On a spike, it first looks for an open GitHub issue whose title or body matches the error signature. If found, it comments the new spike data there; if not, it falls through to creating a deduplicated Linear bug assigned via CODEOWNERS.
When to use it
Use it when your team tracks some work in GitHub Issues and some in Linear, and you don't want a Linear ticket spun up for an error an engineer is already handling in a GitHub issue. Best for repos in a hybrid tracking setup.
How it works
- 1A Sentry spike alert fires for an issue.
- 2The flow builds a search signature from the error type and culprit and queries open GitHub issues.
- 3A branch checks for a match: if a GitHub issue exists, it comments the spike count and Sentry link there and stops.
- 4If no GitHub match, it searches Linear by fingerprint to avoid duplicating there too.
- 5It resolves the owning team from CODEOWNERS and creates or updates the Linear bug accordingly.
Set it up
What you configure once, before turning it on.
- 1Connect SentryErrors, performance, releases.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
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.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
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.