ENGINEERING
Auto-quarantine flaky tests from CI re-run signal
When a GitHub Actions test job fails then passes on automatic retry, this flags the test as intermittent, tags the source file.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub workflow_run completed webhookGitHub
- LogicKeep tests that failed then passed on retry
- ActionResolve test file CODEOWNERGitHub
- ActionOpen owner-assigned flaky quarantine issueGitHub
- OutputComment quarantined tests on the PRGitHub
What it does
It watches GitHub Actions for tests that fail on the first attempt but pass on a retry inside the same run — the classic flaky signature. Instead of letting the green re-run hide the problem, it adds a `flaky` label, comments the failing test name on the PR, and files a quarantine issue assigned to the file's CODEOWNER.
When to use it
Use it when your pipeline retries failed jobs automatically and "eventually green" builds are masking unstable tests. It turns a silent retry into a tracked, owned work item.
How it works
- 1A GitHub `workflow_run` webhook fires when a CI run completes.
- 2A logic step inspects the run's job attempts and keeps only tests that failed-then-passed across retries.
- 3For each flaky test, GitHub is queried for the test file's CODEOWNER.
- 4A GitHub issue is opened with the test name, run link, and failure log, assigned to that owner and labeled `flaky`.
- 5The originating PR gets a comment listing the quarantined tests so reviewers see the instability before merging.
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.