ENGINEERING
Weekly Quarantine Debt Report: Re-Surface Skipped Tests for Cleanup
Each week, lists every currently-skipped/quarantined test from the codebase and its open Linear ticket age.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionScan repo for skipped/quarantined test annotationsGitHub
- ActionFetch linked flake ticket status and age from LinearLinear
- LogicCompute quarantine age; flag stale beyond SLA
- OutputPost aging quarantine-debt digest to SlackSlack
What it does
Quarantining a test is easy; un-quarantining it is what teams forget. This weekly job inventories every skipped test in the repo, matches each to its Linear flake ticket, computes how long it has been quarantined, and posts a Slack digest that pressures owners to either fix it or delete it.
When to use it
Use it when your quarantine list has quietly grown into a graveyard and coverage is silently rotting. It turns invisible skip annotations into a visible, aging backlog with named owners.
How it works
- 1A weekly schedule trigger starts the run.
- 2A GitHub step scans the codebase for skip/quarantine annotations and extracts the linked ticket IDs.
- 3A Linear query pulls each matching flake ticket's status, assignee, and creation date.
- 4A logic step computes quarantine age and flags tickets older than the SLA as stale.
- 5A Slack digest posts the full list sorted by age, highlighting stale entries and their owners for action.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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.