ENGINEERING
Auto-Skip a Confirmed Flaky Test via PR and Notify the Author
When a test is confirmed flaky, opens a GitHub pull request that adds a skip annotation referencing the tracking issue.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: test confirmed flakyHTTP webhook
- ActionResolve last author and file path via GitHub git blameGitHub
- LogicBuild skip annotation linked to tracking issue
- ActionOpen GitHub PR adding the skip markerGitHub
- OutputSlack DM the author to review the auto-skipSlack
What it does
Closes the loop between detection and remediation. Once a test is confirmed flaky, this bot writes the actual code change to skip it — opening a real PR that adds a skip/xfail marker linked to the tracking issue — and pings the engineer who last touched the test so the unblock is reviewed, not rubber-stamped.
When to use it
Use it when flaky tests are blocking merges and you want to unblock the pipeline fast without permanently disabling coverage silently. Every skip is a reviewable PR tied to an issue.
How it works
- 1A webhook fires when a flaky test is confirmed (from an upstream detector or a manual label).
- 2An action uses git blame via the GitHub API to find the test's last author and file location.
- 3A logic step builds the skip annotation referencing the tracking issue number.
- 4An action opens a GitHub PR on a new branch adding the skip marker.
- 5A final output sends a Slack DM to the author with the PR link asking them to review the temporary skip.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect HTTP webhookTrigger any URL on agent actions.
- 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.