ENGINEERING
Nightly flaky-test trend report from Axiom CI logs to Linear
Runs nightly, queries Axiom for the last 7 days of CI test results, ranks tests by intermittent-failure rate.
How it runs
The automated pipeline, trigger to output.
- TriggerNightly schedule
- ActionQuery Axiom for 7-day CI resultsAxiom
- LogicRank by intermittent failure rate
- LogicKeep tests above flakiness threshold
- OutputUpsert one Linear ticket per offenderLinear
What it does
Turns raw CI log history into a ranked flakiness report. Instead of reacting to a single red run, it looks across a rolling window in Axiom, computes each test's pass/fail variance, and surfaces the chronic offenders that waste the most developer time.
When to use it
Use when you already ship CI events to Axiom and want a data-driven, recurring view of which tests are flaky rather than one-off catches. Good for a weekly reliability review or burning down a flaky backlog systematically.
How it works
- 1A nightly schedule triggers the run.
- 2The flow queries Axiom for all test outcomes over the trailing 7 days.
- 3It computes per-test flakiness: tests that both passed and failed on identical commits, ranked by failure rate.
- 4A filter keeps only tests above the configured threshold (e.g. >10% intermittent failures).
- 5For each, it upserts a Linear ticket: creates a new one or updates an existing ticket's failure count and trend.
- 6It posts the ranked summary as the final report.
Set it up
What you configure once, before turning it on.
- 1Connect AxiomLog streams, queries, dashboards.
- 2Connect LinearIssues, projects, cycles, triage.
- 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
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.