ENGINEERING
Flaky Test Detector to ClickUp Tech-Debt Item
Watches GitHub Actions for tests that fail then pass on re-run, confirms the flakiness, and opens a tracked tech-debt task in ClickUp so the intermittent failure does not get lost.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub Actions workflow_run completedGitHub
- ActionFetch job attempts and per-test resultsGitHub
- LogicKeep tests that failed then passed on retry
- ActionSearch ClickUp for existing flaky-test taskClickUp
- LogicSkip if a task already tracks this test
- OutputCreate ClickUp tech-debt task with run linkClickUp
What it does
It catches tests that fail intermittently in CI and turns each one into a tracked piece of tech debt. When a GitHub Actions run reports a test that failed on one attempt but passed on a retry, the workflow flags it as flaky and files a ClickUp task with the test name, the failing job, and a link to the run.
When to use it
Use it when your team re-runs red builds until they go green and the underlying flaky tests never get fixed. This stops the silent erosion of CI trust by making every intermittent failure visible and owned.
How it works
- 1A GitHub Actions workflow_run completes and fires a webhook into the workflow.
- 2The workflow pulls the run's job attempts and compares per-test results across retries.
- 3A logic step keeps only tests that failed on an early attempt and passed later in the same run (the flaky signature).
- 4For each confirmed flaky test it checks ClickUp for an existing open task to avoid duplicates.
- 5If none exists, it creates a ClickUp tech-debt task tagged "flaky-test" with the test path, owning team, and run link.
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.