ENGINEERING
Cross-Repo Consumer Finder for Internal Package Bumps (GitHub)
When a bump PR raises the version of an internally published package, this searches the GitHub org for every other repo that depends on it and reports which downstream repos…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub bump PR webhookGitHub
- LogicDetect internal package + extract new version
- ActionOrg-wide code search for consumer reposGitHub
- LogicCompare pinned versions; flag major gaps
- OutputPost consumer fan-out report on PRGitHub
What it does
Bumping a shared internal library inside its own repo says nothing about the dozen services that consume it. This workflow detects when a bump PR touches an internally published package, then uses GitHub code search across the org to find every repo that lists that package as a dependency, along with the version each is pinned to. It reports which consumers are now behind and which would break on the new major.
When to use it
Use it in an organization with shared internal packages where a maintainer needs to know the fan-out before merging a release-shaped bump, without manually grepping each consumer repo.
How it works
- 1A GitHub PR webhook fires on a bump branch.
- 2A logic step checks whether the bumped package is internally owned (matches the org scope) and extracts the new version.
- 3A GitHub action runs org-wide code search for manifests declaring that package as a dependency.
- 4A logic step compares each consumer's pinned version to the new version and flags major-version gaps.
- 5The workflow posts a consumer-fan-out report as a comment on the source PR.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, 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.