ENGINEERING
Lockfile PR blast-radius reviewer router
When a pull request changes a lockfile, maps each bumped dependency to the services that import it and auto-requests the right code owners as reviewers.
How it runs
The automated pipeline, trigger to output.
- TriggerPR opened or synchronizedGitHub
- LogicFilter to PRs touching a lockfile
- ActionParse lockfile diff for changed packages and versions
- LogicMap packages to affected services and code owners
- ActionRequest owning reviewers and add team labelsGitHub
- OutputPost blast-radius summary comment on the PRGitHub
What it does
Watches pull requests that touch a lockfile (`pnpm-lock.yaml`, `package-lock.json`, `yarn.lock`). It diffs the lockfile to find which packages changed and at what version, maps those packages to the workspace services that depend on them, and requests review from the owning teams. It then posts a single comment summarizing the blast radius so reviewers know exactly why they were tagged.
When to use it
Use it on any monorepo where a one-line lockfile change can silently affect a dozen services and the wrong people end up reviewing (or nobody does). It turns an opaque diff into a targeted, accountable review.
How it works
- 1A pull request is opened or updated on GitHub.
- 2A filter checks whether the changed files include a lockfile; non-lockfile PRs exit early.
- 3The lockfile diff is parsed to extract changed package names and version deltas.
- 4Each package is mapped to the importing services and their CODEOWNERS.
- 5The owning reviewers and team labels are added to the PR via GitHub.
- 6A blast-radius summary comment is posted listing affected services and version jumps.
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
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.