ENGINEERING
Quarantine a Test On-Demand via PR Comment Command
Lets a reviewer comment a /quarantine command on a pull request to instantly skip the named flaky test, resolve its owner, and open a tracked Linear issue without leaving the PR.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub issue_comment webhook on PRGitHub
- LogicMatch /quarantine command and verify commenter access
- ActionCommit skip annotation to PR branchGitHub
- ActionResolve owner from CODEOWNERSGitHub
- ActionCreate assigned Linear issue with deadlineLinear
- OutputReply on PR with confirmation and issue linkGitHub
What it does
Gives engineers a one-line PR command to quarantine a flaky test mid-review. Instead of blocking the merge or manually filing follow-ups, a reviewer types the command and the workflow handles the skip, the owner lookup, and the tracking ticket.
When to use it
Use this during code review when a known-flaky test is failing a PR that is otherwise good. It unblocks the merge in seconds while still creating an owned, deadlined re-enable task.
How it works
- 1A GitHub issue_comment webhook fires on every new PR comment.
- 2A logic step checks the comment body for the '/quarantine <test-name>' command and confirms the commenter has write access.
- 3The workflow commits a skip annotation for the named test onto the PR branch.
- 4It resolves the owner from CODEOWNERS for that test's file.
- 5A Linear issue is created, assigned to the owner, labeled 'flaky-quarantine', linked to the PR, with a 14-day re-enable deadline.
- 6The workflow replies on the PR with a confirmation reaction and the new issue link.
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.