ENGINEERING
High-Blast-Radius Bump Review Ticket Router (Linear)
For dependency-bump PRs whose blast radius crosses a threshold, this opens a Linear review ticket assigned to the owning team with the affected call sites and services attached.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub bump PR webhookGitHub
- ActionCompute call sites + blast-radius scoreShell
- LogicGate: stop if score below threshold
- ActionResolve owning team from CODEOWNERSShell
- ActionCreate routed review issue in LinearLinear
- OutputLabel PR needs-review to hold auto-mergeGitHub
What it does
Low-risk bumps should auto-merge; high-risk ones need a named owner. This workflow scores a GitHub bump PR's blast radius, and only when it exceeds your threshold does it open a Linear issue routed to the team that owns the affected files, pre-filled with the call sites, version delta, and a link back to the PR. The PR is labeled `needs-review` so merge automation holds.
When to use it
Use it when your team wants bump triage off the PR firehose and into the same Linear board you already plan from, with ownership resolved automatically from CODEOWNERS rather than guessed in Slack.
How it works
- 1A GitHub PR webhook fires on a Renovate/Dependabot branch.
- 2A shell step computes the changed package's call sites and a blast-radius score.
- 3A logic gate stops the flow when the score is below the threshold (lets auto-merge proceed).
- 4For high-radius bumps, a step resolves the owning team from CODEOWNERS of the touched paths.
- 5A Linear action creates a triaged review issue with call sites, version delta, and PR link, assigned to that team.
- 6The workflow labels the GitHub PR `needs-review` to block auto-merge.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 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.