ENGINEERING
Quarantine a Flaky Test via PR Comment Command
When an engineer comments `/quarantine <test>` on a pull request, validates ownership, adds the test to the skip-list on a new branch, opens a tracking issue.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub PR comment createdGitHub
- LogicMatch /quarantine command + verify write access
- ActionAppend test to skip-list on a branchGitHub
- ActionOpen labeled tracking issueGitHub
- OutputReply on PR with quarantine confirmationGitHub
What it does
Gives engineers a one-line ChatOps command to quarantine a known-flaky test without leaving the PR. Commenting `/quarantine <test-id>` triggers a flow that validates the requester, parks the test in the skip-list via a committed branch, files a labeled tracking issue, and replies inline with confirmation.
When to use it
Use it when developers already know a test is flaky and just want a fast, auditable way to park it mid-review instead of editing config by hand. It keeps quarantine actions traceable to a person and a tracking issue.
How it works
- 1A GitHub webhook fires on new issue/PR comments.
- 2A filter matches comments starting with `/quarantine` and confirms the author has write access.
- 3It parses the test identifier from the command.
- 4It appends the test to the skip-list file on a branch and pushes the commit.
- 5It opens a tracking issue labeled `flaky-quarantine`, linking the PR and requester.
- 6It replies on the PR thread with the issue link and quarantine confirmation.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, 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.