ENGINEERING
Quarantine Dependabot PRs That Break CI and Triage by Failure Type
When a Dependabot PR's CI run completes, it inspects the result and, for failures, classifies them as flaky-retry, breaking-change, or peer-conflict.
How it runs
The automated pipeline, trigger to output.
- TriggerCheck suite completes on Dependabot PRGitHub
- LogicKeep only failed CI runs
- ActionFetch failing job logs and diffGitHub
- LogicClassify failure: flake / breaking / peer-conflict
- ActionApply quarantine label, re-run flakesGitHub
- OutputPost triage verdict to SlackSlack
What it does
A red check on a Dependabot PR could mean a flaky test, a genuine breaking change, or a peer-dependency conflict — and each needs a different response. This workflow reads the failed CI run, classifies the failure from the logs, quarantines the PR with a clear label, and tells reviewers exactly what kind of problem they're looking at before anyone opens the PR.
When to use it
Run it when dependency-bump PRs frequently fail CI and reviewers waste time opening each one just to discover whether it's a flake or a real incompatibility.
How it works
- 1A GitHub webhook fires when a check suite completes on a Dependabot PR.
- 2A filter keeps only failed runs and ignores green ones.
- 3GitHub fetches the failing job logs and the dependency diff.
- 4A classifier matches log signatures to flaky-retry, breaking-change, or peer-conflict categories.
- 5A branch applies the matching quarantine label and, for flakes, requests a re-run.
- 6A triage note with the verdict and next action posts to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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.