ENGINEERING
Auto-Open a Skip PR for Repeat-Offender Flaky Tests
When a test crosses the flake-count limit it opens a draft PR annotating the test as skipped or quarantined, then files a ClickUp follow-up to unskip after a real fix.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub check run completedGitHub
- LogicCompute rolling flake count past repeat-offender limit
- ActionBranch and apply quarantine annotationGitHub
- ActionOpen draft skip PR referencing failing runsGitHub
- OutputFile ClickUp follow-up to unskip after fixClickUp
What it does
This workflow stops a chronically flaky test from blocking everyone's builds. Once a test's flake count crosses the limit, it opens a draft GitHub pull request that adds a skip or quarantine annotation to that test, then files a ClickUp follow-up task so the skip is temporary and someone is on the hook to fix and re-enable it.
When to use it
Use it when a single flaky test is repeatedly red-X-ing PRs and the team needs immediate relief without losing track of the debt. It suits repos with a quarantine annotation convention and a culture of fixing rather than permanently skipping.
How it works
- 1A GitHub check-run event fires when a CI run finishes.
- 2The flow records the result and computes the rolling flake count for each test that failed then passed.
- 3A branch fires only when a test exceeds the repeat-offender limit and is not already quarantined.
- 4It creates a branch, applies the skip or quarantine annotation, and opens a draft PR referencing the failing runs.
- 5It files a ClickUp follow-up task to fix the root cause and remove the skip, assigned to the test's owner.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect ClickUpDocs + tasks + chats in one workspace.
- 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.