ENGINEERING
Turn a Slack Flaky-Test Report into a Quarantine PR
When an engineer reports a flaky test from a Slack shortcut, it verifies the test exists, opens a GitHub PR that quarantines it, and files a Linear deflake ticket linking both.
How it runs
The automated pipeline, trigger to output.
- TriggerSlack flaky-test report shortcutSlack
- ActionConfirm test path and owner via GitHub search/blameGitHub
- LogicBranch if test not found, request clarification
- ActionOpen quarantine PR skipping the testGitHub
- ActionFile Linear deflake ticket linking report and PRLinear
- OutputReply with PR and ticket links in Slack threadSlack
What it does
It gives engineers a one-tap path from "this test is flaky again" to a real, tracked fix. From a Slack message shortcut they name the test; the workflow confirms the test exists in the repo, opens a GitHub PR adding it to the quarantine skip list, and creates a Linear deflake ticket that links the report, the PR, and the assignee.
When to use it
Use it when flake reports currently die in Slack threads. This captures the human signal at the moment of frustration and converts it into auditable engineering work without anyone leaving chat.
How it works
- 1A Slack message shortcut triggers the workflow with the reported test identifier.
- 2A GitHub action searches the repo to confirm the test path and current owner via blame.
- 3A logic step branches: if the test isn't found, reply asking for clarification and stop.
- 4A GitHub action opens a quarantine PR skipping the test and tagging the owner.
- 5A Linear action files a deflake ticket linking the Slack report and the PR.
- 6A Slack reply confirms the PR and ticket back in the thread.
Set it up
What you configure once, before turning it on.
- 1Connect SlackChannels, DMs, threads, mentions.
- 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.