ENGINEERING
Escalate high-severity transitive CVEs in merged bumps to PagerDuty
Watches merged dependency-bump PRs, and if a bump introduced a critical or high transitive CVE that slipped through.
How it runs
The automated pipeline, trigger to output.
- TriggerDependency-bump PR merged to default branchGitHub
- ActionResolve transitive set and fetch advisoriesGitHub
- LogicKeep only reachable critical/high CVEs
- ActionOpen PagerDuty incident for the CVEPagerDuty
- OutputPost incident and package details to SlackSlack
What it does
Catches the dangerous case where a risky dependency bump already merged. On every merge it re-scores the transitive set, and when a critical or high CVE made it in, it pages on-call and notifies the team channel with the exact package, advisory, and merge commit.
When to use it
Use it as a safety net behind your PR gate. Gates can be overridden, advisories land after merge, and patch bumps get auto-merged. This ensures a newly merged blast radius never sits silently until the next deploy.
How it works
- 1A GitHub event fires when a dependency-bump PR is merged to the default branch.
- 2The flow resolves the transitive packages the merge changed and queries advisories for each.
- 3A logic step filters to only critical and high severity CVEs that are actually reachable.
- 4If none match, the run ends quietly.
- 5If matches exist, it opens a PagerDuty incident tagged with the package and advisory ID.
- 6It posts the incident link plus offending package and merge commit to the engineering Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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.