ENGINEERING
Weekly Transitive Dependency Debt Digest
On a weekly schedule, this scans all repos for outdated and vulnerable transitive dependencies, ranks them by how many services each touches.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionPull dependency manifests and resolved trees from each repoGitHub
- LogicScore each outdated package by service count and advisory status
- ActionPersist ranked debt snapshot to PostgresPostgres
- OutputPost prioritized upgrade backlog to SlackSlack
What it does
Gives engineering leadership a standing, ranked view of dependency debt. It walks every repository's resolved dependency tree, flags packages that are outdated or carry advisories, and scores each one by blast radius — how many distinct services would be touched by the bump.
When to use it
Use it to run a recurring upgrade triage instead of reacting only to emergencies. The ranking lets you spend a fixed weekly budget on the highest-leverage bumps first.
How it works
- 1A weekly schedule kicks off the run.
- 2The flow pulls dependency manifests and resolved trees from each GitHub repo, including transitive packages.
- 3A scoring step counts how many services depend on each outdated package and cross-references known advisories to compute a priority.
- 4Results are written to a Postgres table so trends are queryable over time.
- 5A digest posts the top items to Slack with service counts, current vs. latest versions, and whether an advisory applies.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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.