ENGINEERING
Nightly Flaky-Test Scoring from CI History
Runs nightly to score every test by its pass/fail flip rate over the last 30 days, flags tests above a flakiness threshold.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionQuery 30-day test outcomesPostgres
- LogicScore flip rate and apply threshold
- ActionUpsert quarantine registryPostgres
- OutputOpen or refresh GitHub issue per offenderGitHub
What it does
Each night this workflow analyzes recent CI results to compute a flakiness score per test — how often it flips between pass and fail without code changes. Tests exceeding the threshold are added to a Postgres quarantine registry that your test runner reads, and a GitHub tracking issue is created or refreshed with the latest score and trend.
When to use it
Use this for data-driven quarantine decisions instead of reacting to single failures. It catches slow-burn flakiness that individual runs miss and keeps the quarantine list current as tests stabilize or degrade.
How it works
- 1A nightly schedule triggers the run.
- 2The bot queries the Postgres results table for the last 30 days of test outcomes.
- 3A scoring step computes flip rate and total runs per test, then flags any test over the configured flakiness threshold and de-flags tests that have gone quiet.
- 4It upserts the quarantine registry table so the test runner can skip flagged tests automatically.
- 5For each newly flagged test it opens or updates a GitHub issue with the score, run count, and a 30-day trend summary.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 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.