ENGINEERING
Remind authors to link PRs to a Linear issue
When a PR opens without a linked Linear issue in its title or branch, it comments asking the author to attach one, and stays quiet once a valid issue reference is present.
How it runs
The automated pipeline, trigger to output.
- TriggerPR opened or editedGitHub
- LogicLinear issue key present?
- ActionVerify issue exists in LinearLinear
- OutputComment asking to link an issueGitHub
What it does
This workflow checks new pull requests for a Linear issue reference (like ENG-123) in the branch name, title, or description. If none is found, it confirms against the Linear API that no matching issue exists, then comments on the PR asking the author to link the relevant issue so work stays traceable. PRs that already reference a valid issue are left untouched.
When to use it
When your team tracks work in Linear and wants every code change tied back to an issue for traceability and release planning, but reviewers keep forgetting to enforce it manually.
How it works
- 1A GitHub webhook fires when a PR is opened or edited.
- 2The workflow scans the branch, title, and body for a Linear issue key pattern.
- 3If a key is found, it verifies the issue exists in Linear and ends quietly.
- 4If no key is found, a logic branch routes to the nudge path.
- 5It posts a PR comment asking the author to link a Linear issue, with a short note on why traceability matters.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.