ENGINEERING
Quarantine Expiry Sweep with Linear Sync
A scheduled agent audits all currently quarantined tests, checks whether their deflake deadline has passed.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled quarantine sweep
- ActionScan repo for quarantined testsGitHub
- ActionRead linked Linear issue status and due datesLinear
- LogicSplit on-track vs overdue
- ActionEscalate overdue Linear issuesLinear
- OutputPost per-team summary to SlackSlack
What it does
This workflow stops quarantine from becoming a graveyard. It periodically inventories every test marked quarantined in the repo, cross-references the linked Linear issue and its deflake deadline, and acts: fresh items get a gentle Slack reminder, while overdue items get their Linear issue escalated and the test flagged to be un-skipped so coverage is restored.
When to use it
Use this when quarantined tests accumulate and nobody fixes them. It enforces the deadline side of your quarantine policy automatically, on a weekly or biweekly cadence.
How it works
- 1A scheduled trigger fires the sweep.
- 2An action scans the repo for quarantine annotations and their linked issue IDs.
- 3An action reads each linked Linear issue's status and due date.
- 4A logic step splits tests into on-track versus overdue.
- 5An action escalates overdue Linear issues and bumps priority.
- 6The output posts a per-team summary to Slack with overdue items called out.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.